October 12, 2017 at 2:50 am
Hi,
I have a log shipped database on SQL 2008R2 that last night went into suspect mode & I cannot run checkdb because it reports as in the middle of a restore.
I'm wondering if anyone can point me to a way to get back into standby mode so that my log shipping can continue / I can get in to check the db without killing log shipping.
My concern is the database is log shipped from a 3rd party and getting it set up was painful so trying to get help to maximise my chance of successful recovery (am investigating the cause and logs that we've got around that & it's mitigation).
Thank you.
December 21, 2017 at 12:32 pm
1. Can you provide the errors you're receiving when the secondary attempts to restore the log file?
2. What 3rd party? Do you mean like Idera, RedGate, or Lightspeed?
3. How large is this database?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
December 21, 2017 at 2:28 pm
You can't fix that.
If you do recover the DB and run checkDB, you can't get it back into restoring state, and without running checkDB, it won't come out of suspect.
Drop it, restore a fresh backup from the primary, and then check the IO subsystem and see if you can find what caused the corruption.
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 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply