-
What Is a Hyper-V Failover Cluster?
-
Why Deploy a Hyper-V Cluster?
-
Hyper-V Failover Cluster Requirements
-
How to Create a Hyper-V Failover Cluster with Server Manager
-
How to Create a Hyper-V Failover Cluster with PowerShell
-
Network Best Practices and Health Checks After Setup
-
New Hyper-V Cluster Improvements in Windows Server 2025
-
Protect Hyper-V Environment with a Professional Solution
-
Hyper-V Failover Cluster FAQs
-
Conclusion
When a standalone Hyper-V host fails, every virtual machine on it goes down until the server is repaired. A Hyper-V failover cluster removes that single point of failure: two or more hosts share storage and watch each other, and if one fails, the others restart its VMs automatically.
Quick answer: To set up a Hyper-V failover cluster, install the Hyper-V role and the Failover Clustering feature on two or more Windows Server hosts in the same domain, connect them all to shared storage (iSCSI, Fibre Channel, SMB 3 or Storage Spaces Direct), validate the configuration in Failover Cluster Manager, and create the cluster. Then configure a quorum witness, add the shared disks as Cluster Shared Volumes, and create your VMs on those volumes so they fail over automatically.
What Is a Hyper-V Failover Cluster?
A Hyper-V failover cluster is a group of Hyper-V hosts, called nodes, that work together using the Windows Server Failover Clustering feature. All nodes can access the same shared storage, where the VMs’ files are kept. If a node fails, the cluster automatically restarts its VMs on the remaining nodes. For planned maintenance, you can move running VMs to another node with live migration, with no downtime.
Clusters usually store VMs on Cluster Shared Volumes (CSV), which let every node read and write the same volumes at the same time through a common path such as C:\ClusterStorage\Volume1.
Why Deploy a Hyper-V Cluster?
1. High availability: if a host fails, its VMs restart on another node within minutes, without manual intervention.
2. Maintenance without downtime: move running VMs to other nodes with live migration before patching or repairing a host.
3. Better resource utilization: spread VMs across hosts, and rebalance them as workloads change.
4. Scalability: add nodes as your infrastructure grows, without rebuilding the cluster.
5. Resilience: Windows Server 2025 improves resilience across racks, rooms and even campus-level deployments.
Hyper-V Failover Cluster Requirements
Check that your hardware and software meet these requirements before you start.
Hardware and Software Requirements
At least two servers, ideally with identical hardware
64-bit processors with hardware-assisted virtualization (Intel VT-x or AMD-V) and Data Execution Prevention (DEP) enabled in the BIOS/UEFI
The same edition and version of Windows Server on every node, preferably Windows Server 2022 or 2025 Datacenter, with the same updates installed
All nodes joined to the same Active Directory domain (Windows Server 2025 also supports workgroup clusters)
Static IP addresses on every node
Networking Requirements
Separate networks or VLANs for management, cluster and CSV traffic, live migration, storage, and VM traffic
10 GbE or faster adapters, with at least two per network for redundancy
Switch Embedded Teaming (SET) for redundant virtual switch uplinks
On the storage switch, enable flow control and keep storage traffic isolated from other traffic
Storage Requirements
Shared storage that all nodes can access: iSCSI or Fibre Channel SAN, shared SAS, or Storage Spaces Direct (S2D)
Disks initialized as GPT and formatted as NTFS or ReFS
SSD or NVMe storage for production workloads
Instead of block storage, you can also store VMs on an SMB 3 file share, for example on a Scale-Out File Server. Grant Full Control on the share and its folder to the computer accounts of all cluster nodes and to the cluster name object.
How to Create a Hyper-V Failover Cluster with Server Manager
Step 1. Installing the Hyper-V Role
Repeat this step on every node.
1. Open Server Manager.
2. Click Manage and select Add Roles and Features.

3. Review the notes on the Before You Begin page and click Next.
4. Select Role-based or feature-based installation and click Next.

5. Select the server to install the role on. You can also install roles on remote servers from Server Manager.
6. Select Hyper-V.
7. In the pop-up dialog, check Include management tools (if applicable), click Add Features, and click Next until the installation starts. The server restarts to finish installing Hyper-V.
8. To confirm the installation, open Server Manager > Tools and check that Hyper-V Manager is listed.
Step 2. Install the Failover Clustering Feature
Repeat this step on every node.
1. In Server Manager, click Manage and select Add Roles and Features.
2. Select Role-based or feature-based installation and click Next.
3. Select the server and click Next, then click Next again on the Server Roles page.
4. On the Features page, check Failover Clustering, click Add Features in the pop-up, and click Next.
5. Optionally, check Restart the destination server automatically if required, then click Install.
6. To confirm the installation, open Server Manager > Tools and check that Failover Cluster Manager is listed.
If you use multipath storage, also install the Multipath I/O feature on every node in this step.
Step 3. Connect the Shared iSCSI Storage
The exact steps depend on your storage system. These are the steps for iSCSI storage. Repeat steps 1–8 on every node, so all nodes can see the same disks.
1. Open Server Manager.
2. Click Tools and select iSCSI Initiator.

3. In iSCSI Initiator Properties, open the Discovery tab.
4. Click Discover Portal.
5. Enter the IP address or DNS name of the storage system. Keep the default port (3260) unless your storage uses a different one.
6. Open the Targets tab.
7. Select the discovered target and click Connect.
8. In Connect To Target, check Add this connection to the list of Favorite Targets, so the connection is restored after a restart. If you installed Multipath I/O, also check Enable multi-path.
Then prepare the disk on one node only:
9. Open Server Manager > Tools > Computer Management and select Disk Management.
10. Find the new offline disk, which has the size of the volume you created on the storage system. Right-click it and select Online, then right-click it again and select Initialize Disk, choosing GPT.
11. Right-click the unallocated space and select New Simple Volume. Format it as NTFS or ReFS. You don’t need to assign a drive letter, because the cluster will manage the disk.
12. Don’t bring the disk online on the other nodes. Once the cluster is created, it controls which node owns the disk.
Step 4. Create the Failover Cluster
1. In Server Manager, click Tools and select Failover Cluster Manager.
2. Right-click Failover Cluster Manager in the left pane and select Create Cluster.
3. On the Before You Begin page, click Next.
4. Add all the servers that will be part of the cluster. You can click Browse to search for them in Active Directory.
5. When asked whether to run validation tests, choose Yes and click Next. Validation is strongly recommended, and Microsoft supports only clusters that pass it.
6. Select Run all tests (recommended) and click Next.

7. Confirm the tests to run and click Next. Validation takes a few minutes.
8. When validation finishes, click View Report and fix any errors before you continue. Warnings should also be reviewed.
9. Enter a name for the cluster and a static IP address for cluster management on your management network.
10. Confirm the cluster name, nodes and IP address, and click Next to create the cluster.
11. When the cluster is created, click View Report to check for any problems, then click Finish.
12. The new cluster now appears in Failover Cluster Manager. Under Nodes, check that every node shows the status Up.
Step 5. Configure the Cluster Quorum
The quorum decides whether the cluster has enough votes to keep running, which prevents a “split-brain” situation when nodes lose contact with each other. A two-node cluster always needs a witness.
1. In Failover Cluster Manager, right-click the cluster name and select More Actions > Configure Cluster Quorum Settings.
2. Choose Select the quorum witness, then choose a Disk Witness (a small shared disk of about 1 GB), a File Share Witness on a server outside the cluster, or a Cloud Witness in Azure.
3. Finish the wizard, and check that the witness shows as Online under Cluster Core Resources.
Step 6. Configure Cluster Shared Volumes (CSV)
1. In Failover Cluster Manager, expand Storage and select Disks. If your shared disk isn’t listed, click Add Disk and select it.
2. Right-click the disk and select Add to Cluster Shared Volumes.

The volume now appears on every node under C:\ClusterStorage\, for example C:\ClusterStorage\Volume1. Store your VMs there.
Step 7. Configure Live Migration
1. In Failover Cluster Manager, select Networks, then click Live Migration Settings in the Actions pane. Select the network(s) to use for live migration, ideally a dedicated one, and move it to the top of the list.
2. In Hyper-V Manager, right-click each host, select Hyper-V Settings > Live Migrations, and set the number of simultaneous live migrations. Under Advanced Features, choose SMB as the performance option if your network supports SMB Direct (RDMA), or Compression otherwise.

Live migrations between nodes in the cluster are handled by the cluster. The Enable incoming and outgoing live migrations setting and the authentication protocol (CredSSP or Kerberos) apply to migrations to hosts outside the cluster. If you choose Kerberos, configure constrained delegation for each host’s computer account in Active Directory.
Step 8. Create Hight Available Virtual Machines
1. In Failover Cluster Manager, right-click Roles and select Virtual Machines > New Virtual Machine. Choose the node that will run the VM first.
2. In the New Virtual Machine Wizard, store the VM and its virtual disks on a Cluster Shared Volume, for example C:\ClusterStorage\Volume1, so every node can access them. Finish the wizard as usual.
3. To make an existing VM highly available, first move its files to a CSV, then right-click Roles, select Configure Role, choose Virtual Machine, and select the VM.
4. Test the cluster. Right-click the VM under Roles and select Move > Live Migration > Select Node to move it with no downtime. Then simulate a failure by shutting down a node, and check that the cluster restarts its VMs on another node.
For more ways to improve availability after the cluster is running, see how to configure Hyper-V high availability.
How to Create a Hyper-V Failover Cluster with PowerShell
Step 1. Install Hyper-V and Failover Clustering on all nodes
Invoke-Command -ComputerName H1,H2 -ScriptBlock {
Install-WindowsFeature -Name Hyper-V, Failover-Clustering -IncludeManagementTools -Restart
}
Step 2. Validate the configuration
Test-Cluster -Node H1,H2

Review the report that’s generated and fix any errors before you continue.
Step 3. Create the cluster
New-Cluster -Name HVCLUSTER -Node H1,H2 -StaticAddress 192.168.10.100
Step 4. Configure the quorum witness
Use a file share on a server outside the cluster:
Set-ClusterQuorum -FileShareWitness "\\FS01\ClusterWitness"
Step 5. Configure Cluster Shared Volumes
Get-ClusterAvailableDisk | Add-ClusterDisk Get-ClusterResource Add-ClusterSharedVolume -Name "Cluster Disk 1"
Use the disk name shown by Get-ClusterResource. Don’t add the witness disk, if you use one, to CSV.
Step 6. Make a VM highly available
Add-ClusterVirtualMachineRole -VMName "VM01"
The VM’s files must already be on a Cluster Shared Volume.
Network Best Practices and Health Checks After Setup
Network Design
Separate management, cluster/CSV, live migration, storage and VM traffic with dedicated adapters or VLANs.
Use Switch Embedded Teaming (SET) or multiple adapters for redundancy, and RDMA-capable adapters for SMB storage and live migration where possible.
Enable jumbo frames only if every switch and adapter on the path supports them.
In Failover Cluster Manager > Networks, check that each network has the right role: cluster only, cluster and client, or none (for iSCSI networks).
Health Checks
Check that all nodes, roles and volumes are up:
Get-ClusterNode Get-ClusterGroup Get-ClusterSharedVolume
Review Cluster Events in Failover Cluster Manager after any change, such as patching or adding hardware.
Run
Test-Clusteragain after major changes, and keep the report.Test live migration and failover regularly, not just after the initial setup.
Use Cluster-Aware Updating to patch nodes one at a time without downtime.
New Hyper-V Cluster Improvements in Windows Server 2025
Windows Server 2025 introduces several clustering improvements:
Enhanced Storage Spaces Direct resiliency: improved storage fault tolerance and campus cluster support for clusters spread across rooms or buildings.
GPU-P live migration: VMs using GPU partitioning can now be live migrated between nodes, which helps AI and graphics-intensive workloads.
Live migration in workgroup clusters: Hyper-V clusters can run without Active Directory and still support live migration, using certificate-based authentication. This is useful for edge and branch-office deployments.
Faster failure detection: improved hang detection and cluster responsiveness reduce the time services are interrupted.
Protect Hyper-V Environment with a Professional Solution
A Hyper-V failover cluster keeps VMs running when a host fails, but it doesn’t protect your data from deletion, corruption or ransomware, because all nodes use the same shared storage. To keep your data safe, back up your VMs with a professional backup and recovery solution.
Vinchin Backup & Recovery is a professional solution that backs up VMs on VMware vSphere, Hyper-V, XenServer, XCP-ng, oVirt, RHV, OpenStack and more, as well as databases, NAS, file servers, and Linux and Windows servers.
For Hyper-V, including clustered VMs, Vinchin Backup & Recovery provides agentless incremental backup, data reduction, backup node expansion, offsite backup copies and more.
It can also migrate VMs across any virtualization platforms, including VMware, XenServer and most KVM-based hypervisors, so you can move workloads between platforms as your infrastructure changes.
To backup Hyper-V VM, you just need to:
1. Select Hyper-V VM

2. Select backup storage

3. Select backup strategies

4. Submit the job

Vinchin Backup & Recovery has been selected by thousands of companies and you can also start to use this powerful system with a 60-day full-featured trial! Also, contact us and leave your needs, and then you will receive a solution according to your IT environment.
Hyper-V Failover Cluster FAQs
Q1: Which network ports must be open between cluster nodes?
Open UDP and TCP port 3343 for cluster communication, plus RPC (TCP 135), SMB (TCP 445), the dynamic RPC range (TCP 49152–65535), and ICMP between all nodes. Live migration uses TCP 6600 when it isn’t sent over SMB. Windows Firewall rules for these are created automatically when you install the Failover Clustering feature, but check any firewalls between the nodes.
Q2: Can I mix different CPUs or network adapters in a Hyper-V cluster?
You can, but it’s not recommended. Different CPU generations can block live migration unless you enable processor compatibility mode on the VMs, which hides newer CPU features. Different network adapters can cause inconsistent performance. Use identical hardware where possible.
Q3: What’s the difference between Quick Migration and Live Migration?
Quick Migration saves the VM’s state, moves it, and resumes it on another node, which causes a short interruption. Live Migration copies the VM’s memory while it keeps running and switches over with no noticeable downtime. Use Live Migration whenever continuous service matters.
Q4: Can I add more nodes to the cluster later?
Yes. Prepare the new server the same way (Hyper-V, Failover Clustering, network and shared storage), then in Failover Cluster Manager right-click Nodes and select Add Node, or run Add-ClusterNode -Name H3. Run validation when prompted.
Q5: Is a failover cluster the same as a backup?
No. A cluster keeps VMs running when a host fails, but all nodes use the same shared storage, so deleted files, corruption or ransomware affect every node. You still need regular VM backups stored outside the cluster.
Conclusion
A Hyper-V failover cluster keeps your virtual machines available when a host fails and lets you maintain hosts without downtime. Prepare matching servers and shared storage, validate and create the cluster, configure a quorum witness and Cluster Shared Volumes, and create your VMs on those volumes. Then test failover and keep an eye on cluster health.
To protect the data inside your cluster against deletion, corruption and ransomware, back up your VMs with Vinchin Backup & Recovery. Try it free for 60 days.
Share on: