Two-Node Hyper-V Failover Cluster
Two Windows Servers running the company's virtual machines as one cluster, so a failed host or a patch reboot moves the VMs instead of stopping the business.
Most small-business servers are one physical machine running several virtual machines. When that machine needs a patch, a part, or simply fails, everything on it stops with it. This project removes that single point of failure without moving the business to the cloud.
What we built
Two Windows Servers joined into one Windows Server Failover Cluster, hosting the company's Hyper-V virtual machines on shared storage. Each VM runs on one node at a time; the cluster watches both nodes continuously.
- Automatic failover. If a node fails, its virtual machines restart on the other node on their own, without anyone being called.
- Maintenance without downtime. Windows updates, firmware and hardware work are done one node at a time. VMs are live-migrated to the other node first, so users never notice.
- Balanced load. Under normal operation the VMs are spread across both nodes, so each server does half the work and has headroom for the other half.
- Monitored and backed up. The cluster joins the client's managed environment: cluster health, storage and every VM are monitored, and the VMs are backed up like any other server.
Who it is for
A company that already runs its line-of-business systems on a server in the building and cannot afford an unplanned outage, but does not want the monthly cost of moving everything to a data center. Two servers and shared storage are a one-time purchase; the availability is ongoing.
Part of our Managed IT server work. Ask us whether your servers are a candidate.