InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 02:22:30 GMT20http://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxBecause you do "Tail log backup on ServerA with "NORECOVERY"".Mon, 22 Apr 2013 18:03:27 GMTpan123auhttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxLast night while migrating a 2TB database we came across the same issue:Database 'DBname' cannot be opened. It is in the middle of a restore.Error: 927, Severity: 14, State: 2.A system process, SPID 46, with sa login and task as DBMIRROR was "connected" to the old database that is in restoring mode. How does that happen when I put it into Single User and then did a TAIL backup of the log and put it into restoring mode? Every two minutes in the error log SPIDS 14, 15, 16, 17 alternately keep trying to open the restoring database and generating that error. The migrate strategy we used was database log shipping to the new disk and last night we brought the secondary online as primary. This database also was mirroring to a partner server, I removed that at the very beginning. These are the steps taken to migrate the database:--ensure most recent log shipped backup was restored--via GUI remove MIRRORING from the primary--put in SINGLE_USER mode--via GUI, change name of db from Primary to Primary_OLD--take TAIL of log backup, Primary_OLD goes into restoring mode--restore TAIL to Primary_NEW WITH RECOVERY--via GUI, rename Primary_NEW to Primary--put back into MULTI_USER modeSo it is now successfully working on the new disk, but we have the lingering error every two minutes as noted. We have checked all the mirroring monitors/tables and even ran ALTER DB...PARTNER OFF etc and it all states there is no mirroring configured.This will be resolved when we decide to drop the Primary_OLD database...but it is a little bothersome seeing that connection and the open errors when they should not be happening, would be nice to know what is causing this. Thanks.Sat, 20 Apr 2013 10:39:48 GMTlouislamour2673http://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxLiterally all I have is a SQL Error Log full of:Database 'DBname' cannot be opened. It is in the middle of a restore.Error: 927, Severity: 14, State: 2.I see nothing when I run profiler, no stored procedure calls just that exception approximately every 2 minutes. As I mentioned in my previous post I'm wondering if it is, indeed anything to do with log shipping. As far as both servers were concerned, log shipping was correctly configured in one direction with SPs and reports showing expected results. Having failed back I'm not now having this issue on the new (original) secondary despite following exactly the same process.Thu, 14 Feb 2013 16:31:21 GMTMissTippsInOzhttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspx[quote][b]MissTippsInOz (2/14/2013)[/b][hr]However I did, and still believe its necessary[/quote]The idea is to keep the 2 way configuration in place as the document states.From the error it sounds like an agent task is trying to access the new secondary database. Can you post more detail from the logs please.Thu, 14 Feb 2013 16:17:31 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxYou're absolutely right; it doesn't. However I did, and still believe its necessary, and ran them again on failback and have no problems so, rightly or wrongly, it doesn't help in getting to the bottom of my issue.Thu, 14 Feb 2013 16:07:22 GMTMissTippsInOzhttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxThe link I posted does not tell you to run sp_delete_log_shipping_primary_secondary or sp_delete_log_shipping_primary_database for the role reversal!!Thu, 14 Feb 2013 15:51:45 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxJust thought I'd add that I failed back this morning using exactly the same process and I'm not now seeing these errors occur on the secondary. Suspect that the errors may have been unrelated to log shipping in the first place, but still not got to the bottom of it.Thu, 14 Feb 2013 15:38:39 GMTMissTippsInOzhttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxSorry I gave general process when I should have been specific. All steps in that article are covered. Databases all appear in the correct log shipping system tables and don't appear anywhere they shouldn't. As far as everything I know and can see goes, I am running with reverse log shipping and only reverse log shipping. And yet..every two minutes I get the error in the log.Thu, 14 Feb 2013 05:14:11 GMTMissTippsInOzhttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspx[quote][b]MissTippsInOz (2/13/2013)[/b][hr]HiI'm currently running some DR testing and have failed over a couple of databases to our DR site. Generally the process was:Tail log backup on ServerA with NORECOVERYRESTORE with RECOVERY on ServerB[/quote]Correct up to and including this point. When failing over Log Shipping scenarios, consult the following documentation [url=http://msdn.microsoft.com/en-us/library/ms178117(v=sql.105).aspx][u][b]http://msdn.microsoft.com/en-us/library/ms178117(v=sql.105).aspx[/b][/u][/url]Thu, 14 Feb 2013 02:23:32 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1419754-1549-1.aspxHiI'm currently running some DR testing and have failed over a couple of databases to our DR site. Generally the process was:Tail log backup on ServerA with NORECOVERYRESTORE with RECOVERY on ServerBRan sp_delete_log_shipping_primary_secondary and sp_delete_log_shipping_primary_database on ServerACreated reverse log shipping on ServerB to log ship back to ServerAAll looks good and functions.....BUTI've got a log full of 927 errors on ServerA from 'sa': "Database 'MyDB' cannot be opened. It is in the middle of a restore."What is trying to access it? Have I not successfully 'killed' log shipping on ServerA?I'm sure (hopeful) this is stupid simple and I'm just being brainless. ThanksClareWed, 13 Feb 2013 15:11:44 GMTMissTippsInOz