Hello,
I have a SQL alwaysON setup between on-prem and Azure SQL server (IaaS). Its a 2 node cluster and have configured file share witness for the quorum( On one of the Azure server). There is a site-to-site VPN configured to facilitate all these.
Of late , we see our primary DB going down due to instability in cluster. It was noticed that our network goes down there by making secondary node and file share in accessible and cluster gets affected . Due to which all the primary DBs becomes in accessible and application downtime.
This setup was primarily built for DR purpose and accordingly we have placed the quorum on Azure side.
How can we avoid this situation. I assume all this is due to unavailability of Azure node and File share witness ( this too on Azure) are in accessible at the same time whenever network goes down.
Is there any configuration changes I can make to make the on-prem stable irrespective of the status of secondary node.
what quorum method I should adapt for these kind of situation. Please help.