Verify whether the virtualization center was added using a VIP (Virtual IP). If it was not added via a VIP, it is possible that the primary node's direct IP was used instead, and the primary node has since failed over to a different host.
• Remediation Steps:
Delete the existing virtualization entry and re-add it. Note that backup tasks will need to restart from a full backup, as the UUID of the newly added virtualization center will have changed.
Alternatively, update the virtualization center's IP address to the VIP directly within the database. Operational steps:
1). Stop all active backup tasks, then add the new virtualization center using the VIP.
2). Access the database to retrieve the UUID of the newly added virtualization center (execute select * from vm_vcenter\G); copy the corresponding UUID associated with the VIP address.
3). Replace the vcenter_uuid values in both the vm_machine_list and vm_backup_timepoint tables with the new UUID:
update vm_machine_list set vcenter_uuid='uuid';
update vm_backup_timepoint set vcenter_uuid='uuid';
4). Delete the original virtualization entry (the one not added via the VIP), and then resume the backup tasks.
