For a 2-node cluster, you must have a quorum witness (disk witness or file share/cloud witness) to avoid split-brain scenarios. Since you have an MSA SAN, a Disk Witness is the best fit.
Here’s the step-by-step to create and configure a quorum disk witness using your HPE MSA 2060:
- Prepare the Quorum Disk on the MSA
- Log in to the MSA 2060 SMU (Storage Management Utility).
- Create a new volume (LUN) on your storage pool.
- Keep it small (typically 1–2 GB is enough for a witness).
- Present this LUN to both cluster nodes.
- Assign the same LUN ID on all paths for consistency.
- Ensure multipath (MPIO) is installed and working on both nodes.
- Configure the Quorum Disk in Windows
On both nodes:
- Open Server Manager → Tools → Computer Management → Disk Management.
- Bring the new LUN online, initialize it (GPT or MBR), and create a simple volume (format NTFS/ReFS).
- Assign a drive letter (temporary, e.g.,
Q:). - Name it something like ClusterQuorum.
- Assign a drive letter (temporary, e.g.,
- Don’t store any data on it — it’s reserved for cluster use.
- Add the Disk to the Cluster
On one node:
- Open Failover Cluster Manager (FCM).
- Go to Storage → Disks → Add Disk.
- You should see the new LUN available.
- Add it to the cluster.
- It will now appear under Cluster Disks.
- Configure Quorum Settings
In FCM, right-click the cluster name → More Actions → Configure Cluster Quorum Settings.
Choose Select the quorum witness → Configure a disk witness.
Select the quorum disk you just added.
Finish the wizard.
=> Your quorum disk is now active.
- Verify
- In FCM → Cluster Name → Nodes, check that both nodes are Up.
- Under Cluster Core Resources → Disk Witness, confirm it shows Online.
- Run Validate a Configuration (from FCM → right-click cluster) to ensure your storage/network passes all checks.
Tip: In 2-node clusters, using a disk witness is generally preferred if you already have shared storage. Alternative options:
- File Share Witness (on a 3rd server, not part of the cluster).
- Cloud Witness (uses Azure).