Forum Discussion
Availability Group failover issue
Hello, We ran into an issue recently that caused a three-node availability group to fail. We're running SQL Server 2019 (RTM-CU32-GDR) on Windows Server 2019 Standard (version 1809). We're trying ...
It looks like Node B wasn’t fully ready when the auto-failover happened, even though it was in sync. SQL requires all databases to be “failover ready,” and if one lags or isn’t joined, it won’t switch. Best to check is_failover_ready, review failover policy (FailureConditionLevel/health timeout), and do regular manual failover tests to be sure secondaries can take over.
MS Article: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-flexible-automatic-failover-policy?view=sql-server-ver17
Also verify that all databases in the availability groups exist on node B.