Symptoms

Assume that you have an Always On Availability Group (AG) in an instance of Microsoft SQL Server 2016 or 2017. When you back up a secondary replica that is running under asynchronous-commit mode, the backup operation may fail occasionally. Additionally, you may receive the following error message:

Error: 9003, Severity: 20, State: 1.

The log scan number (nnn:nnn:nnn) passed to log scan in database 'dbname' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

Resolution

This problem is fixed in the following updates for SQL Server:

          Cumulative Update 13 for SQL Server 2017

          Cumulative Update 4 for SQL Server 2016 Service Pack 2

Cumulative Update 11 for SQL Server 2016 Service Pack 1

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

Latest cumulative update for SQL Server 2017

The latest build for SQL Server 2016

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 Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×