September 28, 2015 at 12:01 pm
Hi,
DR plan for primary database in a hosted cloud environment. The secondary is on another network. Version is SQL Server 2008R2 (10.50.2550.0) Enterprise.
Log Shipping runs fine for a few restores, then I come back the next day, and I see "A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state." And the restore job continues to fail. No further restores go through.
I checked the primary db with DBCC and there are no errors. I reconfigured LS twice, and the last time, added a 5-minute delay for the restore job. Same thing happens every time.
I could really use some help knowing where to look for the issue.
Graeme
October 7, 2015 at 10:38 am
At the direction of an expert, I am putting this question onto Stack Exchange. Thanks.
November 1, 2015 at 5:43 am
Did you check the log shipping monitor tables?
What is the status of secondary DB?
November 1, 2015 at 11:39 am
Did you check SQL errorlog/event logs to see is there was any corruption or any other issues ?
Also do run the DBCC checkdb command.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply