September 9, 2008 at 3:22 pm
My DBA took another position last week and now I have a problem. We are running SQL 2005 Enterprise and are using log shipping. Everything was working fine, until last night when log shipping began to fail and I started getting notifications every 2 minutes. It appears that one of the logs did not get moved over from over 12 hours ago. I copied the file over and ran "RESTORE LOG XXXFROM DISK = 'F:\MSSQL\TRANSLOGS\xxx\xxx_xxxxxxxxxx.trn' from the notes I was left. This ran. After restoring this log I had hoped the others would restore automatically. Wrong. The restore took the 2ndary db out of standby/readonly mode and now log shipping fails because the 2ndary is active.
What are my options? Is there a way to re-synch to 2ndary and then re-enable log shipping? Am I in awful shape and now I should just delete the old db and go through the Log shipping wizard again starting with a db backup? Or is there another option.
Any help would be appreciated.
Michael
September 9, 2008 at 9:19 pm
If you restored without using the NORECOVERY option, there's nothing you can do. You brought the database out of standby and log shipping can't restart. I'd delete it and run through the wizard again.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply