December 24, 2015 at 10:24 am
Good Morning Experts,
In log shipping, what will happen when the primary database goes to suspect state? How to handle this scenario?
December 24, 2015 at 11:02 am
The first thing is probably to fail over to the secondary somehow. Then determine what caused the suspect state. Have you checked the error log?
Fail back will require moving backups to the primary and restoring it up to date, then re-enabling log shipping. There isn't a simple procedure as it depends on how much downtime and how you will move traffic from one instance to the other.
December 24, 2015 at 11:59 pm
Since the primary database went to suspect state, log shipping will not work, am i correct?
January 5, 2016 at 2:19 pm
Yes, no log backup should be possible on the database when it is suspect.
January 6, 2016 at 11:13 pm
When the database goes to suspect state, it cannot be backed up(Full/Diff/Tlog), correct?
January 7, 2016 at 2:13 am
You might be able to take a tail-log backup by switching to Emergency mode, but no full or diff, and you probably wouldn't want to backup a corrupt database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply