The availability group databases are changing roles from “PRIMARY” to “RESOLVING” during VMWare Snapshot

After activating Availability Groups, Windows Cluster Failover Service might fail during the snapshot period of VM backup. While Veeam backup is being taken, snapshot holds server and SQL AlwaysOn listener may act like it lost its secondary replica and error messages like below can be received. With the instant effect of snapshot, SQL Server change databases’ status to resolving. After SQL Server will automatically bring it back to normal state but there will be a downtime. During this period, login attempts will not be successful.


AlwaysOn Availability Groups connection with secondary database terminated for primary database ‘Database_Name’ on the availability replica with Replica ID: {feddedc3-c4bc-4c7e-b00f-a3fc21623b99}. This is an informational message only. No user action is required

For fix it, below commands can be executed in PowerShell on one of the cluster member. This commands will increase time out values for cluster. If snapshot progress getting longer on guest system, values need to be change.



Import-module failover clusters

—–change the same-site heart beat to 2 seconds

(get-cluster).SameSubnetDelay = 2000

—–change the cross-site heart beat to 4 seconds

(get-cluster).CrossSubnetDelay = 4000

—–change the same-site ping loss threshold to 10 lost pings

(get-cluster).SameSubnetThreshold = 10

—–change the cross-site ping loss threshold to 10 lost pings

(get-cluster).CrossSubnetThreshold = 10

(get-cluster).RouteHistoryLength = 20

2 thoughts on “The availability group databases are changing roles from “PRIMARY” to “RESOLVING” during VMWare Snapshot

  1. Johnb19

    Hi there! This is my first visit to your blog! We are a group of volunteers and starting a new initiative in a community in the same niche. Your blog provided us beneficial information to work on. You have done a marvellous job!


Leave a Reply

Your email address will not be published. Required fields are marked *