none
2019 Hyper-V Cluster - Quorum RRS feed

  • Question

  • Hi All,

    I just finished setting up a hyper-V cluster in our environment, a 3 node cluster.

    since the cluster node count is "Odd" will it still be recommended rather necessary to put a witness (disk) in this case?

    what i normally practice is to only put a witness when the cluster counts is "even" (for tie-breaking)

    hopefully you can share me your thoughts

    Thanks

    Saturday, November 9, 2019 12:14 AM

All replies

  • I would.

    With a witness you can lose a server, then another and still stay up.

    https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/understand-quorum

    Just don't put the witness on a share on one of the nodes.


    Charlie Coverdale

    Disclaimer: You take sole responsibility for any actions you take based on my posts.


    Saturday, November 9, 2019 12:22 AM
  • Hi,

    In a cluster with an odd number of nodes, you can go without a cluster witness, however with the failover cluster's dynamic quorum technology you would in general want to have a witness.

    You can read more about it in the link Charlie linked above, you'll also find some more information over here:
    https://docs.microsoft.com/en-us/windows-server/failover-clustering/manage-cluster-quorum


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, November 9, 2019 12:34 AM
  • Hi, I am just hosting VM in this cluster.

    how many nodes can i afford to lose on a 3 node cluster w/o a witness? - from what i know i can afford to lose 1 and the cluster service will still be up.

    In a 3n+1w setup does that mean i can afford to lose 2? and cluster service will still be intact?

    Thanks

    Saturday, November 9, 2019 2:46 PM
  • Hi, I am just hosting VM in this cluster.

    how many nodes can i afford to lose on a 3 node cluster w/o a witness? - from what i know i can afford to lose 1 and the cluster service will still be up.

    In a 3n+1w setup does that mean i can afford to lose 2? and cluster service will still be intact?

    Thanks

    Saturday, November 9, 2019 2:46 PM
  • Check the links provided:

    Reference:
    Understanding cluster and pool quorum


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, November 9, 2019 4:03 PM
  • Hi,

    Was your issue resolved? 

    If you resolved it using any above solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 11, 2019 3:15 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using any above solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 13, 2019 1:52 AM
  • 

    i added a disk witness , this is the first time i encountered this in a hyper-v cluster. is this normal?

    i didnt notice this on my 2016 cluster

    Thursday, November 14, 2019 3:12 PM
  • The Disk Witness can be any dedicated drive on a shared storage configuration that is supported by the cluster and passes the Validate a Cluster tests.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 14, 2019 3:25 PM