April 4, 2023 at 1:09 pm
Hi,
I've SQL 2019 STD with CU16 on Win 2019 STD. i had some ESXI host unresponsive for 5 sec and the SQL AlwaysOn become completely malfunction that both my SQL Server the databases that are part of the AlwaysOn are i the state of restoring. the "funny" thing is that the AlwaysOn configuration completely disappear from both server. there was nothing in those DMV sys.dm_hadr_availability_group_states ,sys.availability_groups ,sys.availability_groups_cluster,sys.dm_hadr_availability_replica_states ,sys.availability_replicas ,sys.dm_hadr_availability_replica_cluster_states .
how this can be happened?
THX
April 5, 2023 at 8:42 am
We had a similar issue but it only dropped the AG from one of the replica's recently which was bad enough. Take a read of the following article and see if you have any of the errors listed in the article. In "rare" situations SQL will drop a replica from an AG.
We had to drop the AG from the node that used to be secondary and recreate the AG. I'm guessing you had to create the AG from scratch to restore service?
There are a couple of other recent posts on here with people also experiencing vanishing AG's.
April 5, 2023 at 2:26 pm
onetsql,
Nice link. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply