Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Log shipping - Fails after daily maintenance jobs - restore from a known good backup

$
0
0

Microsoft SQL Server 2014 - 12.0.4100.1 (X64)   Apr 20 2015 17:29:27   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) 

Log-Shipping works fine whole day with default 15 minutes interval

However, soon daily maintenance jobs (DBCC, Indexing etc) runs on live during off-peak hour and LS_Restore try to apply TRN logs generated after that maintenance, it fails only for couple of databases - NOT for ALL DBs from same Primary server to same secondary server

Following is the error in LS_restore job history

Date12/05/2016 01:45:00
LogJob History (LSRestore_LSSeconday\SQLDB1_ReportDatabaseLive)

Step ID1
ServerLSSeconday\SQLDB3
Job NameLSRestore_LSSeconday\SQLDB1_ReportDatabase
Step NameLog shipping restore log job step.
Duration00:01:17
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0

Message
2016-05-12 01:46:16.99*** Error: Could not apply log backup file '\\dbbackups\transaction_logs\ReportDatabaseLive\ReportDatabase_20160512003001.trn' to secondary database 'ReportDatabaseLive'.(Microsoft.SqlServer.Management.LogShipping) ***
2016-05-12 01:46:16.99*** Error: An error occurred while processing the log for database 'ReportDatabaseLive'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'ReportDatabaseLive' (14: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.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'ReportDatabaseLive', file 'ReportDatabaseLive_Data' on file 1.
Processed 1 pages for database 'ReportDatabaseLive', file 'ReportDatabaseLive_Log' on file 1.(.Net SqlClient Data Provider) ***
2016-05-12 01:46:16.99*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2016-05-12 01:46:16.99*** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2016-05-12 01:46:17.01Skipping log backup file '\\dbbackups\transaction_logs\ReportDatabaseLive\ReportDatabase_20160512003001.trn' for secondary database 'ReportDatabaseLive' because the file could not be verified.
2016-05-12 01:46:17.01*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2016-05-12 01:46:17.01*** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2016-05-12 01:46:17.01The restore operation was successful. Secondary Database: 'ReportDatabaseLive', Number of log backup files restored: 0
2016-05-12 01:46:17.01*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2016-05-12 01:46:17.01*** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2016-05-12 01:46:17.01Deleting old log backup files. Primary Database: 'ReportDatabase'
2016-05-12 01:46:17.01*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2016-05-12 01:46:17.01*** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***

So any thoughts please?

thanks.


For quick review of new features, try virtual labs: http://msdn.microsoft.com/en-us/aa570323


Viewing all articles
Browse latest Browse all 4689

Trending Articles