April 12, 2016 at 2:24 pm
I am trying to setup log shipping for about 50 databases across 2 SQL 2014 servers.
I'm getting intermittent errors when it is attempting to restart the db.
The actual error log is below:
2016-04-12 19:19:43.39 spid60 Error: 17066, Severity: 16, State: 1.
2016-04-12 19:19:43.39 spid60 SQL Server Assertion: File: <recovery.cpp>, line=5062 Failed Assertion = 'ckptEnd->GetCkptBeginLsn () == m_SeenCkptBegin'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2016-04-12 19:19:43.39 spid60 Error: 3624, Severity: 20, State: 1.
2016-04-12 19:19:43.39 spid60 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
2016-04-12 19:19:43.63 spid60 Error: 3414, Severity: 21, State: 1.
2016-04-12 19:19:43.63 spid60 An error occurred during recovery, preventing the database 'xxxxxxx' (25:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Most of the time this process works fine and when it does happen it happens against a different db every time.
Details:
- both SQL versions are 12.0.4439.1
- 50 dbs on an Azure server (on SSD drives) doing log backups every 15 minutes to a location accessible to a local server (also running SQL 2014)
- Every 10 minutes those .trn files are getting copied locally to our local server
- Every 1 hour I'm doing a restore on all the files
- I'm doing recovery with standby so we can use the local server for reporting purposes
- Instead of having a 3 jobs for every database (backup, copy, restore) I've created one backup job that loops through all the databases and does backups (same thing for copies and restores) - I did this because I was thinking that this was a timing issue where all these jobs started at the same time.
I should also note that the above error isn't the only error I see when a restore fails. Sometimes it just give me the following:
2016-04-13 01:21:24.31 spid61 Starting up database 'xxxxxxxx'.
2016-04-13 01:21:27.19 spid61 Error: 9004, Severity: 16, State: 6.
2016-04-13 01:21:27.19 spid61 An error occurred while processing the log for database 'xxxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2016-04-13 01:21:27.19 spid61 Error: 3414, Severity: 21, State: 1.
2016-04-13 01:21:27.19 spid61 An error occurred during recovery, preventing the database 'xxxxxxx' (38:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
April 12, 2016 at 11:07 pm
Hope this article will help give you some idea about the error: https://support.microsoft.com/en-us/kb/3027860
April 13, 2016 at 2:07 pm
Thanks for the response. I did see that article and we have sp1 installed already.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply