Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

Server 2012 Two Node Cluster - Disk Witness?

$
0
0

I am in the process of setting up a new 2012 two node cluster for a Hyper-V workload using shared iSCSI (CSV) storage.  Everything is working fine and I was able to Live Migrate and failover test VM's.  Only questions remain about the Quorum and Witness setup.

The Cluster Quorum Wizard wants to set the quorum configuration to Node Majority with no Witness.  When it is set this way the Cluster Validation wizard gives a warning that "The recommended quorum configuration for the current number of nodes is Node and Disk Majority." and "This quorum will be able to sustain failures of 0 nodes."

I created a 1GB NTFS volume on the SAN and enabled multiple connections and have both Nodes connected to the volume (no drive letter assignment).  I can manually set it to use the witness volume and then it will pass the validation.  It actually shows the volume as a voter separate from the nodes stating the following "This quorum model will be able to sustain failures of 1 node(s) with the disk witness online and 0 node(s) when the disk witness goes offline or fails."

With this setup upon a single node reboot I see a warning "Node and Disk Majority (Witness) - Warning: Failure of a node or 'Witness' will cause the cluster to fail.  Check the disk and the nodes." in the Quorum Configuration section of the cluster summary.  I assume this is saying that the single node remaining will stay online in the cluster as long as the witness remains online which should be a good thing.

A side concern is that if the witness volume is a NTFS file system, and from my understanding without CSV setup (which it says the witness cannot be a CSV corruption can occur if both nodes write to the volume.

I look forward to your feedback.  Thank you.


Viewing all articles
Browse latest Browse all 6672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>