Quorum Mode - Node majority (no witness) vs Witness

Cooper, David A. [ISS] (Contractor) 111 Reputation points
2024-04-03T01:22:22.7+00:00

My company's Windows admin team sets up WSFC for our Always On clusters. Our Always On SQL 2019 cluster is typical 3-node cluster with 2 HA nodes in Data Center "A" and 1 DR node in Data Center "B". I asked the sys admins in the past if they created a disk witness, and they said no. As far as I can tell from looking at Failover Cluster Manager and cluster validation report, indeed there is no disk witness. It seems like the cluster is dynamic quorum with each node having a vote. I need to know if the node votes with no disk witness is best practice for my 3-node cluster, and safe? Or should I request reconfiguring with a disk witness? I read something in a MS article that confuses me on this topic... "If it is suitable for your cluster, and there is cluster shared storage available, the cluster selects a disk witness. This option is recommended in most cases, because the cluster software automatically chooses a quorum and witness configuration that provides the highest availability for your cluster." Does the shared storage referenced in that passage need to be on a separate network share, i.e., not on one of the 3 nodes? How can I verify if the WSFC is indeed using a witness on shared storage? Thanks

SQL Server | Other
{count} votes

3 answers

Sort by: Most helpful
  1. Net Runner 620 Reputation points
    2024-04-03T12:37:26.8733333+00:00

    I need to know if the node votes with no disk witness is best practice for my 3-node cluster, and safe?

    In most cases, a 3-node cluster does not require additional witnesses and uses node majority mechanics to maintain its quorum. However, your situation is somewhat specific since the 3rd node is located in a different data center. That means that if the connectivity to that remote location is lost and one of the 2 HA nodes in Data Center "A" goes down for whatever reason (failure, patching, maintenance), the entire cluster will stop https://www.starwindsoftware.com/blog/understand-failover-cluster-quorum.

    Does the shared storage referenced in that passage need to be on a separate network share, i.e., not on one of the 3 nodes?

    In order to avoid the situation described above, you can set up a separate network share located on any other machine within the same Data Center "A" or use your existing two nodes and a free virtual SAN software to create a "shared-nothing" witness disk for clustering purposes https://www.starwindsoftware.com/vsan.

    How can I verify if the WSFC is indeed using a witness on shared storage?

    If a disk or share witness is configured, WSFC automatically switches to external witness quorum maintenance instead of node majority.

    1 person found this answer helpful.
    0 comments No comments

  2. LiHongMSFT-4306 31,566 Reputation points
    2024-04-03T02:41:23.38+00:00

    Hi @Cooper, David A. [ISS] (Contractor)

    See this doc: WSFC Quorum Modes and Voting Configuration (SQL Server)

    When using an asymmetric storage configuration for Always On availability groups, you should generally use the Node Majority quorum mode when you have an odd number of voting nodes, or the Node and File Share Majority quorum mode when you have an even number of voting nodes.

    SQL Server exposes several system dynamic management views (DMVs) that can help you manage settings related WSFC cluster configuration and node quorum voting.

    For more information, see: sys.dm_hadr_cluster, sys.dm_hadr_cluster_members, sys.dm_os_cluster_nodes, sys.dm_hadr_cluster_networks.

    Best regards,

    Cosmog Hong


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

  3. Net Runner 620 Reputation points
    2024-04-03T12:13:48.8+00:00

    (double post, removed)

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.