November 8, 2012 at 11:01 am
Hi ,
We have a very large database which is in recovery mode and transaction log backups have been restored in "WITH CONTINUE_AFTER_ERROR",Is there any way that I can use this database(as secondary) in Log shipping?When I enabled the Restore Log(related to Log Shipping setting) job ,I recieved the following error message:
System.Data.SqlClient.SqlError: A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option. (Microsoft.SqlServer.Smo)
Thanks
November 9, 2012 at 2:15 am
You would have to create your own sort of logshipping which restores the logs with the continue_after_error clause, standard log shipping wants the DB to be consistant, so you if you want to use native log shipping, you will need to restore the database and logs "without" the continue_after_error clauses.
November 9, 2012 at 9:36 am
I would strongly recommend getting a fresh backup and restoring again. If a backup was restored with continue after error, it suggests there was an error somewhere in the restore sequence. That's not exactly something you want in a HA/DR server.
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