High availability From Business
When a VM host fails, Nodekeeper restarts supported virtual machines on a healthy host and keeps their IP and MAC addresses. When a Windows iSCSI node fails, the iSCSI service fails over automatically. Each kind of failure has its own recovery path, described below.
Business: $29 per node per month after the free first month. Card required, once per account; cancel before day 30 and you are not charged.
On this page: VM hosts · Windows iSCSI · By failure · What it needs · Plan
After a host failure, Nodekeeper restarts supported virtual machines (KVM and Proxmox VE) on a healthy host, with the same IP and MAC address, so there is less manual recovery work. The VM starts again from its disk on distributed storage; it is a restart, not a live migration.
Recovery time depends on your detection settings, the number of hosts, storage and network. See the recovery workflow in the product tour.
Windows office PCs boot their system disk over iSCSI. The iSCSI service supports automatic failover, so a node failure takes less manual work to recover from. Linux PCs that are already running map their disks from distributed storage directly.
Windows and Linux network boot for office PCs · Distributed storage
| What failed | How Nodekeeper helps |
|---|---|
| A KVM or Proxmox VE host running HA VMs | Fence the host, then restart its VMs on a healthy host with the same IP and MAC. Memory contents are not carried over; data already on disk is kept. |
| A disk or a storage host | Distributed storage keeps serving from replicas or erasure-coded chunks; you replace the disk and the cluster rebuilds. |
| One room of a two-room cluster | Stretch mode (two rooms plus an arbiter) keeps the cluster available. |
| The Windows iSCSI service for office PCs | Automatic iSCSI failover. Linux PCs that are already running talk to distributed storage directly. |
| An office PC's own hardware | After the old PC is fenced, the user's cloud PC starts on another compatible PC. |
| The Nodekeeper admin node | The storage data plane and running VMs keep working; control-plane operations resume when the admin node is back. |
| Deletion, corruption or a lost cluster | Replicas copy damage too, so use snapshots for undo and backups, including full cloud PC disk backup, for recovery. |
HA VM disks on distributed storage managed by Nodekeeper.
Enough free CPU and memory on the remaining hosts to start the VMs of a failed one.
A healthy storage monitor quorum and working fencing; without them the controller does not act.
With the NK mesh (EVPN), the same address works on the new host.
VM high availability covers KVM and Proxmox VE VMs on Nodekeeper-managed distributed storage. It does not cover ESXi VMs, LXC containers, Proxmox VE corosync clusters, VMs on a LAN pool or behind NAT, or VMs sold through WHMCS. After a failover, check CDN and port-forwarding entries on other nodes.
VM high availability, Windows iSCSI failover, distributed storage and snapshots are part of Business and are not sold as separate add-ons. Licensing is per node.
After the free first month: $29 per node per month. The trial covers up to 3 nodes; for a larger cluster, tell us what you plan to build. Related: Distributed storage · Virtualization · Backups
Manage websites, office PCs and servers from one panel on your own hardware.