Hi @kedar giri
Not sure if this post can help you.
https://geekshangout.com/sql-availability-group-setup-the-local-node-is-not-part-of-quorum/
Best regards,
Percy Tang
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello Everyone,
In One of our clients, the is only two windows servers, and our responsibility was to Deploy failover cluster and on top of that we have to deploy always-on on SQL Server, the environment is something like they have SQL-PROD and SQL-DR which are in different subnet, I have deployed Failover cluster and also deployed always on in SQL server. after couple of day the SQL-DR(DR) suddenly shutdown which lead to SQL-Prod (Primary Server) database to inaccessible state. the issue was something like
The local node is not part of quorum and is unable to initiate a failover. This could be caused by one of the following reasons:
• The local node is not able to communicate with the WSFC cluster.
• No quorum set exists across the WSFC cluster.
For more information on recovering from quorum loss, see SQL Server Books Online.
(Microsoft.SqlServer.Management.HadrTasks)
After SQL-DR(DR) was UP then, everything went normal, primary server was accessible. what might be the issue??
failover manually does not have any issue but, shutting down lead to the SQL-PROD (Primary) to inaccessible, so what might be the possible solution.
Note: -There is no active directory or DNS servers. There environment is exactly that I have mention above scenario.
Hi @kedar giri
Not sure if this post can help you.
https://geekshangout.com/sql-availability-group-setup-the-local-node-is-not-part-of-quorum/
Best regards,
Percy Tang
There was no vote majority so we added fileshare witness and problem was resolved