A Failover Cluster is a group of independent devices that work together to increase the availability of applications and services. The clustered nodes are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Microsoft Failover Clustering is always in an active/passive configuration. This means that any single role can only operate on a single cluster node at any given time. A cluster can operate multiple roles simultaneously, however. Depending on the role type, it may be possible for roles to operate independently on separate hosts. In Hyper-V, an individual virtual machine represents a role, distinct from the entire Hyper-V service. Therefore, a single virtual machine (VM) can only run on one Hyper-V host at any given time, but each host can run multiple virtual machines simultaneously.
Enhancing Availability with Hyper-V Cluster for Virtual Machines
If a host crashes, it triggers an automatic restart of virtual machines on another cluster host. However, Hyper-V virtual machines are not considered fault-tolerant as they cannot run on two hosts simultaneously. Installing the Hyper-V cluster ensures highly available and scalable Hyper-V production workloads in the organization network.
See the following guides on how to set up a VM via PXE boot on a Generation 1 VM and how to set up a VM via PXE boot on a Generation 2 VM, how to deploy images to computers or virtual machines using WDS and Windows deployment cannot continue, the operating system is missing via MDT deployment.
You can install the Hyper-V role through PowerShell, Dism.exe, and Server Manager. Therefore, we will share the steps for a power shell and a DISM. Kindly refer to this guide: How to install and Configure Hyper-V on Windows Server on Windows Server 2019, and 2022 via the Server Manager, PowerShell or DISM. Here is a guide on how to install “How to install free Hyper-V Server in Core Mode on a VMware Workstation”. Here is a guide on how to install “How to install free Hyper-V Server in Core Mode on a VMware Workstation“.
Furthermore, we have installed the Hyper-V role on both Hyper-V hosts. We need to install the Failover Clustering feature on both servers in our lab. However, You may want to see the hardware requirements and storage options for failover clustering. Moreover, Perform the below steps on the Windows Server before installing Hyper-V and configuring Failover Clustering.
- Apply essential patches (Windows Update), use correct PC Name, and configure Basic networking.
- Ensure that the device joins the domain.
In addition, If you do not have a new Server, you can clone an existing VM and Sysprep it to eliminate the system-specific information. Nonetheless, Here is a guide on how to do it “How to Clone and Sysprep (generalize ) a Windows Server running on VMware Workstation“. Here are some other articles that might interest you: Sysprep (Generalize) a Windows installation: How to perform Sysprep in Windows, and how to clone a Windows Server running on VirtualBox.
Part 1 – Installing the Failover Clustering: Access the first (1st) Hyper-V node. If you wish you can install Hyper-V Clustering via PowerShell: This is the quickest way to set up a failover cluster feature on the Hyper-V servers.
Install-WindowsFeature Failover-Clustering –IncludeAllSubFeature –IncludeManagementTools 
Access the second (2nd) Hyper-V node: On the second server, also install the HyperV cluster feature. There are quite a few different ways to add the HyperV roles via the Server Manager.
- You can either click on the Local Server, then click on Manage and finally, click on Add Servers and features.
- Alternatively, click on the Dashboard on the Server Manager and Click on Add roles and features.
On the “Before you begin” page, you can click on Next. If you do not want the page to appear subsequent times, check the button to skip the page by default.
On the next Window “Select installation type“, select “Role-based or feature-based installation” and click on “Next“.
If you have multiple servers, please ensure you select the right server to have the Failover Cluster installed.
– I only have one server, therefore it is selected by default.
As you can see below, I have already previously installed the hyper Role. Therefore, on this screen, I will be skipping this window.
Select the Failover Clustering feature and a new window will be promoted
On the “Add the features that are required for Failover Clustering”, click on Add Feature
As we can see, the feature is selected. Click on Next to continue.
Click the install button. For this, the “Restart the destination server automatically if not required”. Just click on “Restart the destination server automatically if required” so you know how it works.
Note: You don’t need a restart for this installation, but I want to demonstrate the process. Upon clicking on “Restart the destination server automatically if required”, you will be prompted to select Yes or No if you wish to automatically restart.
Click “Install” on this window to install Failover Clustering onto the server.
As you can see, we are currently installing Failover Clustering. You can click on close at this point.
Failover Clustering has a Failover Cluster Manager. Use this tool to establish and manage failover clustering. It deals with roles, nodes, storage, and networking for the cluster. The tool is not specific to Hyper-V, but it shares much of the same functionality for controlling virtual machines.
Part 2 – Validate a Hyper-V Cluster:
Before creating a cluster, we strongly recommend that you validate your configuration. Validation helps you confirm that your servers, network, and storage configuration meets specific requirements for failover clusters.
Via PowerShell
Open an administrative PowerShell session by right-clicking the Start button and then selecting Windows PowerShell (Admin).
– To validate the Servers “HyperV and TechWindows2022“, for Failover Clustering, run the command. Ensure to replace the nodes with yours!
Test-Cluster -Node "HyperV","TechWindows2022"
Via Server Manager
Choose the Tools drop-down and select Failover Cluster Manager. In Failover Cluster Manager, go to the middle column under Management and choose Validate Configuration.
This window is informational. You can also choose to not show this page “Before you begin” again by check the box.
In the Select Servers or a Cluster window, add in the names of the two machines that will be the nodes of the cluster. For example, if the names are HyperV and TechWindows2022, enter the name and select Add.
- You can also choose the Browse button to search Active Directory for the names. Once both are listed under Selected Servers, choose Next.
As you can see below, both servers are being selected and will be added.
Below is an output window, showing the two nodes we will be validating. To proceed, click on Next as shown below.
Below is an output window, showing the two nodes we will be validating. To proceed, click on Next as shown below.
Select the Run all test (recommended). This is the most thorough form of validation, that Microsoft expects for complete support. Click on Next to proceed.- Note: If you select to run only tests I select, it allows you to specify a subset of available tests.
On the Confirmation page, it will give you the listing of all the tests it will check.
– Choose Next to begin the test.
The tests will begin and the progress will be displayed as shown below. The overall test battery can take quite some time to complete.
Reviewing and Adapting Test Results on the Summary Page
Once completed, the Summary page appears after the tests run. While still on the Summary page, click View Report and read the test results. Make any necessary changes in the configuration and rerun the tests.
- If the following error is prompted, please refer to the following guide: Connectivity to a writable domain controller from node could not be determined because of an error: The distinguished name of the node could not be determined.
- Click on Finish.
To view the results of the tests after you close the wizard, see SystemRoot\Cluster\Reports\Validation Report date and time.html.
Part 3 – Create Hyper-V Cluster via the Failover Cluster Manager
Open Server Manager and select Failover Clustering from Tools Menu and Select tools and then click on Failover Cluster Manager. Ensure the following prerequisites are met before creating a Failover Cluster.
– All nodes must have at least one IP address and must be in the same subnet.
– The Failover Clustering role must be installed on all servers. In my case, they are HyperV and TechWindows2022.
– Management operating system on all nodes must be the same version and properly patched.
– The nodes “HyperV and TechWindows2022” must be in the same domain and organizational unit.
– For computer account creation, your user account needs proper privileges in the organizational unit or pre-staging the account. If this prerequisite is not met, you may have the following error: Failover Cluster Manager failed while managing one or more clusters, the error was unable to determine if the computer exists in the domain.
Via PowerShell
Open an administrative PowerShell session by right-clicking the Start button and then selecting Windows PowerShell (Admin).
- Run the following command to create the cluster if you are using static IP Addresses. For example, the machine names are HyperV and TechWindows2022, the name of the cluster will be TechDACluster, and the IP Address will be 192.168.xxx.124.
New-Cluster -Name TechDACluster -Node "HyperV","TechWindows2022" -StaticAddress 192.168.xxx.124
If you are using a DHCP, run the following command below to create the cluster. For example, the machine names are HyperV and TechWindows2022, and the name of the cluster will be TechDACluster.
New-Cluster -Name TechDACluster -Node "HyperV","TechWindows2022"Via the Server Manager
From Server Manager, choose the Tools drop-down and select Failover Cluster Manager.
When Failover Cluster Manager opens, it should automatically bring in the name of the cluster you created. If it does not, go to the middle column under Management and choose Connect to Cluster. Input the name of the cluster you created and OK.Select “Create Cluster” under the action menu to create the Failover Cluster.
The window below is just informational. You can also choose to not show this page “Before you begin” again by check the box.
In the Select Servers, add in the names of the two machines that will be the nodes of the cluster. For example, if the names are HyperV and TechWindows2022, enter the name and select Add.
– You can also choose the Browse button to search Active Directory for the names. Once both are listed under Selected Servers, choose Next.
As shown below, we’ve selected the first node (HyperV) server for imminent addition.
If you already know the server FQDN or server name only, enter the name in the field and click on Add as shown below.
– As you can see, this is very straightforward provided you have the needed rights in AD to add the Computer Object.
Below, successfully add the Hyper-V servers (hosts). Click on Next to continue.
Note: On the next page, you will be required to create an administrative computer name and IP address. This Computer Object and its IP address are not as vital for a Hyper-V cluster as they are for other cluster types because the VMs (virtual machines) will not be accessed via the cluster. However, they are still required.
Configuring Cluster Details and Active Directory Integration
Type a Cluster Name and IP Address for the cluster. If you are using a pre-staged account, ensure that you use identical spelling. The matching object created in Active Directory is the cluster’s Computer Name Object (CNO).
– Click “Continue” after finishing to proceed.
You can select the checkbox to add all eligible storage to the cluster as part of the process and then click on Next
The next window displays a progress bar while building your cluster. It will move to the Summary page when done, with a View Report button showing all creation steps. this can help you troubleshoot any errors that occur. Like the validation wizard, all nodes save the report in C:\Windows\Cluster\Reports.
As you can see below, we have the option to View Report to check details of the cluster creation process.
– Click on the Finish button to complete the Cluster setup.
As you can see on the Server Manager, both of our nodes successfully configured servers for High Availability.
Open the Failover cluster and Select the Nodes Option to View the nodes available with the cluster.
If you ever wish to shut down the Cluster. You can find this option under the Action Tab or the More Actions menu. This will completely stop the cluster.The interface itself presents a simple Yes/No dialog window.
– You can also Destroy a Cluster. This option completely removes the cluster object from AD and deletes the cluster’s configuration from the nodes. Before you proceed with this option, make sure you remove all roles. Similar to the Shut Down Cluster command, there is only a simple dialog. Below are the steps to Shut Down or Destroy a Cluster.
Part 4 – Configure Cluster Quorum: Windows Server Failover Clustering provides high availability for workloads. These resources are considered highly available if the nodes that host resources are up; however, the cluster generally requires more than half the nodes to be running, which is known as having a quorum. Quorum is designed to prevent split-brain scenarios, which can happen when there is a partition in the network. Subsets of nodes cannot communicate with each other or there is a problem with communication between subsets of cluster nodes so that multiple servers don’t try to simultaneously host a resource group and write to the same disk at the same time which can lead to numerous problems.
Maintaining Node Consistency through Quorum in Failover Clustering
However, this is prevented with Failover Clustering’s concept of quorum, which forces only one of these group of nodes to continue running, so only one will stay online.
- Quorum determines the number of failures the cluster can sustain while remaining online.
- By having this concept of quorum, the cluster will force the cluster service to stop in one of the subsets of nodes to ensure that there is only one true owner of a particular resource group. Once nodes that have been stopped can again communicate with the main group of nodes, they will automatically rejoin the cluster and start their cluster service.
Failover Clustering supports three types of Quorum Witnesses:
- Cloud Witness: Blob storage in Azure accessible by all nodes of the cluster. It maintains clustering information in a witness.log file, but doesn't store a copy of the cluster database.
- File Share Witness: A SMB file share that is configured on a file server running Windows Server. It maintains clustering information in a witness.log file, but doesn't store a copy of the cluster database.
- Disk Witness: A small clustered disk which is in the Cluster Available Storage group. This disk is highly-available and can failover between nodes. It contains a copy of the cluster database. A Disk Witness isn't supported with Storage Spaces Direct.Designing Quorum and Storage Configuration in Two-Node Failover Clusters
For a two-node failover cluster, the storage should contain at least two separate volumes (LUNs) if using a witness disk for quorum. The witness disk is a disk in the cluster storage designated to hold a copy of the cluster configuration database. The quorum configuration will be Node and Disk Majority for this two-node cluster example. Node and Disk Majority means that the nodes and the witness disk each contain copies of the cluster configuration, and the cluster has quorum as long as a majority (two out of three) of these copies are available.
Note: You will be requiring a shared disk that will be accessible across all Hyper-V Server to configure as Quorum Witness
– Right Click on the Cluster
– Select More Actions and
– Click on Configure Cluster Quorum Setting as shown below.
The window below is just informational. You can also choose to not show this page “Before you begin” again by check the box.
Furthermore, On the Select Quorum Configuration window, we have got three options. I will be selecting the first one as shown below.
– Follow through with the next steps to complete the Cluster Quorum setup.
Part 5 – Configure Clustered Shared Volume (CSV Disk):
However, CSV (Cluster Shared Volumes) is a feature in Windows Server in which shared disks are concurrently accessible to all nodes within a failover cluster. Moreover, You need to tell the cluster manager which storage should be used for the CSVs. Here we will be using the CSVs to hold disks for fault-tolerant VMs.
Furthermore, To complete these steps, the CSV disk should be accessible to all the nodes (HyperV and TechWindows2022) and be a valid disk in the Disk Management snap-in window.
– To enable a CSV on a disk, open the Failover Cluster expand the Storage node select the Disks node. However, select the cluster disk that you want to use as a CSV, and click the Add to Cluster Shared Volumes link in the Actions pane. Moreover, This will create a mount point for the CSV in the system drive.
Follow through with the next steps to complete the Clustered Shared Volume (CSV Disk) configuration. Nonetheless, you may need to extend a volume. In addition, kindly refer to these guides on how to do this: Initialize and format a virtual disk: How to add and remove a new virtual disk from a VM on VMware Workstation, how to extend a VM’s Hard Disk on VMware Workstation, and how to install and configure iSCSI Target Server and iSCSI Initiator on a Windows Server.
I hope you found this blog post helpful. Consequently, Please let me know in the comment session if you have any questions.
