"The log backup chain is broken" error when the log backup process fails in SQL Server

In your Log shipping configuration, the log backup process may fail because of underlying storage and infrastructure issues. In this situation, the log backup process is retried, and this could overwrite a potentially valid log backup file. When this happens, you could experience a break in the log backup chain that may require you to perform a complete reinitialization of your Log shipping configuration. Depending on the size of your databases, this may be a very costly operation.

Additionally, errors that resemble the following are logged in the SQL Server error log:
date time,Backup,Unknown,BACKUP failed to complete the command BACKUP LOG database_name. Check the backup application log for detailed messages.

date time,Backup,Unknown,Error: 3041 Severity: 16 State: 1.

date time,spid326,Unknown,The log backup chain is broken. You must perform a full database backup before you can perform a log backup.

date time,spid326,Unknown,The operating system returned error 170 (The requested resource is in use.) to SQL Server during a write at offset 0x00000009dde000 in file file_path. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information see SQL Server Books Online.

The fix for this issue is included in the following cumulative updates for SQL Server:

Note After you apply this update, the intention is to remove the override of a valid transaction log backup. Therefore, this update introduces some additional validations to check whether the log chain remains unbroken.
Recommendation: Install the latest cumulative update for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3162858 - Last Review: 09/21/2016 03:19:00 - Revision: 6.0

Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Standard

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3162858