Symptoms
After starting a SureBackup job, it stops almost immediately with the following error:
Error: No host is compatible with the virtual machine.
When a host leaves Maintenance Mode, is patched, or experiences a temporary issue (i.e., outages, hiccups), the powered off virtual lab can lose its “home” host. From vCenter’s point of view, the VM now sits inside the vApp folder but is orphaned—no ESXi host currently owns it. The moment Veeam asks vCenter to start the appliance, the placement engine evaluates every host in the cluster, finds no valid target, and throws the “No host is compatible” fault.
Quick Fix
In your vCenter:
- Right-click on the virtual lab, choose Migrate, then Change compute resource only, and select a host.
- Wait for the registration task to finish (it’s instant – no storage move).
- Rerun the SureBackup job. If the virtual lab powers on in vCenter – the problem is solved.
SureBackup’s “No host is compatible”, in most cases, is simply an orphaned lab appliance. A quick migration—even to the same host—will help associate the virtual lab with the host and fix this error.
For further assistance, contact our support team at support@managecast.com.
