VMware: hosts taken over by vCenter
Found while testing 0.42.2 in the lab: when an ESXi host that BackupZit already backs up directly is added to vCenter, two things change on it.
- Its certificate — accept the new one with the button that 0.42.2 added on the Agents page.
- The IDs of VMs created on the standalone host — vCenter gives them an instance UUID, so BackupZit saw them as different VMs and the job failed with "does not exist on this host (any more)". BackupZit now recognises such VMs by their old ID too, and moves the jobs to the new ID automatically at the next refresh of the host.
The VMware page of the user guide explains this in all 14 languages.
Update the console and then the agents (Agents → Update all).
Releases are signed with the BackupZit release key; consoles verify them before installing.
