Hi Guys
I am having an issue with an SQL Availability Group and am wondering if you can lend a hand troubleshooting:
I have 2 SQL Servers on 2017 running on 2012R2.
I have set them up in an Always on Availability Group with Availability mode set to Synchronous Commit and Readable secondary set to No.
I thought this was all working fine but when I was doing something unrelated in Microsoft SQL Management Studio I noticed that the Availability Replicas status for the secondary had a red cross by it. I then checked the availability group dashboard and can now see under the secondary:
Synchronization status: Not Synchronizing
Failover Readiness: Data Loss
This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.
The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database should be in the SYNCHRONIZED state.
I have checked firewall ports and 5022 is open and not blocked. I have also checked netstat to confirm sqlsrvr.exe is using 5022 which it is. I am now starting to think this could be permission related.
Can anyone help point me in the right direction on where to go from here?
Many thanks!