FIX: Transaction log backup failure on the secondary replica in SQL Server 2012 Always-On Availability Groups

Applies to: SQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 Enterprise Core More

Symptoms


Assume that you are using Microsoft SQL Server Always-On availability groups (AG). When you take a transaction log backup on the asynchronous secondary replica, you may encounter a backup failure with an error message that resembles the following:

Backup detected log corruption in database xx. Context is FirstSector. LogFile: x x:\xx_log.ldf' VLF SeqNo: xx VLFBase: xx LogBlockOffset: xx SectorStatus: xx LogBlock.StartLsn.SeqNo: xx LogBlock.StartLsn.Blk: xx Size: xx PrevSize: xx

If you retry a couple of times, the log backup may complete successfully.

Resolution


Cumulative Update Information for SQL Server:

This issue is fixed in the following cumulative update for SQL Server:

       Cumulative Update 7 for SQL Server 2016 RTM

       Cumulative Update 4 for SQL Server 2016 SP1

       Cumulative Update 6 for SQL Server 2014 SP2

       Cumulative Update 13 for SQL Server 2014 SP1

       Cumulative Update 9 for SQL Server 2012 SP3   

Service Pack Information for SQL Server 2012:

This issue is fixed in the following service pack for SQL Server:

          Service Pack 4 for SQL Server 2012

For more information about how to obtain the latest service pack, see How to obtain the latest service pack for SQL Server 2012

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.