https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyOTY3IiwiaGFzaCI6IjI1NTdkYWIyLTM3ZDEtNDY5OC04Mzg4LTI2Nzc2Y2I0ZjRjNCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Transaction Log Backup Job for Microsoft SQL Server with AlwaysOn Availability Groups fails after installing CU15 for SQL Server 2017

Challenge

When utilizing Always On Availability Groups on a Windows Server Failover Cluster using Microsoft SQL Server 2017 and after installing Cumulative Update package 15 (CU15) for SQL Server 2017, Veeam Transaction Log Backup Jobs may fail with the following error message in the the statistics window for the transaction log backup job:

Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID '' is not found in the WSFC data store. The availability group may have been dropped, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation has failed. Please use DROP AVAILABILITY GROUP command to clean up previously failed operations before retrying the current operation.

Cause

The error is a result of a known issue in CU15 for SQL Server 2017.  Please see the section on Availability Group Preferred Replica Backups.
The issue has been resolved in the hotfix linked below.
KB ID:
2967
Product:
Veeam Backup & Replication
Version:
Any
Published:
2019-06-26
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later