KB4056821 - FIX: Log shipping fails when you use it together with Always On Availability Groups in SQL Server 2016 and 2017

Applies To
SQL Server 2016 Service Pack 1 SQL Server 2016 Standard - duplicate (do not use) SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2017 Developer on Windows SQL Server 2017 Enterprise on Windows SQL Server 2017 Enterprise Core on Windows SQL Server 2017 Standard on Windows

Symptoms

When you use log shipping together with Always On Availability Groups in Microsoft SQL Server 2016 and 2017, log shipping can't detect available replica and fails with the following error message:

Note

The backup operation on database 'DatabaseName' was skipped because it is part of an availability group and not its preferred backup replica

Resolution

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

Cumulative Update 4 for SQL Server 2017

Cumulative Update 7 for SQL Server 2016 SP1

About cumulative updates 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:

Latest cumulative update for SQL Server 2017

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