Product Tour: Bring Services Back with Less Manual Work

When a VM host fails, Nodekeeper restarts supported virtual machines on a healthy host and keeps their IP and MAC addresses. When the iSCSI node behind Windows office PCs fails, the Windows iSCSI service takes over automatically. Either way, there is less to do by hand.

From Business High-availability failover for KVM and Proxmox VE virtual machines

Live Demo: try a real panel

Free, no sign-up. It opens a real Nodekeeper panel with a demo account and password already filled in — just click Log in. You can create a website and preview it, and add a domain and DNS records. Data resets daily at 20:30 UTC, and the demo is shared with all visitors, so please do not enter personal information. For safety these are disabled: changing the account or password, two-step verification, adding users, firewall rules, backup restore, ordering and billing management, uploads over 64 MB, and browsing server folders. We recommend opening it in a private window so it does not mix with a panel you are already logged in to.

Live Demo

How VM failover works

  1. Detect. A host stops reporting. Nodekeeper collects evidence from more than one source before it decides the host is down, rather than just cut off from the master.
  2. Decide. In confirm mode an administrator confirms in the panel; in automatic mode the controller proceeds on its own when its safety checks pass.
  3. Fence. The old host is blocked from the VM’s disk on distributed storage, so the old copy cannot keep writing.
  4. Restart. A healthy host is chosen and the VM is started there with the same IP and MAC address.
  5. Verify. The VM is checked until it answers again.
  6. Reconcile. When the failed host comes back, its stale VM definition is quarantined before fencing is lifted.

Windows iSCSI takeover

Windows office PCs boot their system disk over iSCSI from a Nodekeeper site node. The Windows iSCSI service supports automatic takeover, so a node failure no longer means someone has to rebuild the service before people can work.

Linux office PCs map their disk from distributed storage directly and do not depend on the iSCSI node.

Different failures, different recovery

Recovery by failed component
What failsWhat Nodekeeper doesKeep in mind
A KVM or Proxmox VE host running HA VMsFence the host, then restart its VMs on a healthy host with the same IP and MACA restart, not live migration: anything only in memory is lost, data already written to disk is kept
The site node serving iSCSI to Windows office PCsThe Windows iSCSI service fails over automaticallyOpen Windows sessions may need to reconnect
An office PC’s own hardwareAfter the old PC is fenced, the user’s cloud PC can be started on another compatible PCPrograms and unsaved work on the failed PC are not moved
Limits and prerequisites
  • VM failover covers KVM and Proxmox VE VMs whose disks are on Nodekeeper-managed distributed storage, in an HA group with spare capacity.
  • Not covered: ESXi, LXC containers, Proxmox corosync clusters, hyperconverged hosts, and VMs on a LAN pool or behind NAT.
  • If a service is published through a CDN site or port forwarding on another node, check that path separately after a failover.
  • High-availability failover is not sold through WHMCS.

Read more: virtual-machine recovery · KVM, Proxmox VE and ESXi management · Windows and Linux network boot · Infrastructure · Start a Business trial

Tell us which websites, office PCs or infrastructure you want to manage and we will arrange a walkthrough. Please do not send passwords, keys or customer data.

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
support@host.mw WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.