"Failed to update VM properties", "host already exists" general errors after Upgrade/Restore of vCenter or deploying a new vCenter - unable to update


When you upgrade, replace, or deploy a new vCenter or modify it in such a way that the UUID or Instance ID changes and the changed information is not transmitted to Unitrends, a disassociation occurs.


When you upgrade or deploy a new vCenter or modify it in such a way that the UUID or Instance ID changes, Unitrends is no longer can communicate with vCenter. Any action that requires an updated to the tables that validate ESXi hosts, vCenter, or Guest VMs will generate an error concerning communication or update failure such as:

  • Failed to update VM properties.
  • Cannot add ESXi hosts after adding vCenter... host already exist. and Unable to upgrade issues​.
  • May be missing VMs or Jobs fail indicating the VM could not be reached.


If you are using the Legacy /recoveryconsole/ Administrative Interface, please make the following notes:

In new HTML5 /ui/ = How to accomplish with Legacy /recoveryconsole
  • Protected Assets  = Settings > Clients, Networks, and Notifications > Clients
  • Replication = Jobs > Backup Copy (this is considered a Hot copy, because deduplication continues).
  • Archives = Jobs > Backup Copy (this is considered a Cold copy, as the data is rehydrated <un-deduplicated>)
  • Inventory Sync = Select the vCenter in the Navigation Pane, then click on Backups (big icon on the top). On the bottom of the Schedule pane under the list of VMs, you will see two arrows in a circle. Click this icon. Once completed, do the same for the under the Navigation pane. Again refresh the Schedules VMs.
  • Backup Copy Target (adding NAS) = Storage > Storage and Retention > Storage > Add Archive Storage

The instructions below assume you are using the new HTML5 /ui/ Web Administrative Interface.

PART 1: To correct the issue your Unitrends Data Protection Unit (DPU) must be running version 9.1 or newer. Only then should you proceed with these next steps:
  1. Ensure your  Unitrends appliance is on the current release to ensure proper operations and supportability.
  2. Add all ESXi hosts related to any Guest VMs you are protecting using the CONFIGURE > Protected Asset (tab) on the Unitrends. You must select Virtual Hosts > VMware as the Hypervisor Type, and use the username of root and the password for that root user on the ESXi hosts.
  3. Edit the Protected Asset for vCenter and re-enter the password, then save.
  4. Perform an Inventory Sync to load the updated data from the vCenter: Click the Options icon User-added image on top right of the page and select "Inventory Sync"
If you are still getting errors, then the tables are corrupted. Proceed with part 2.

PART 2: Removing and adding vCenter while reducing the risk of current backup data loss:
  1. In the event of data loss, we strongly recommend that you have a recent Cold Backup Copy. If you do not have this in place, you can add a NAS as Backup Copy Target and create a Backup Copy Job, select the newly added NAS and choose the Now option for the schedule. This will run once, creating a copy of the data for the VMs you selected.
  2. If you are currently Replicating the virtual backups, you are covered. However, the step above does give you localized protection and faster restores.
  3. Delete the vCenter from the Protected Assets page. (You MUST delete the Backup schedules as well as uncheck the vCenter/VMs from the Archive schedule.
  4. Add vCenter back to the Client page. Create the schedules.
  5. Verify everything is working as expected.
Protecting VMware Environment: To ensure your VMware environment is fully protect and runs efficiently,
  1. Add all ESXi hosts that are related to the Guest VMs that you wish to protect, to the Protected Assets or Clients Page. Once added, you will see the VMs that are associated to each ESXi (in the Legacy Interface, you must click in the gears icon at the bottom of the Navigation pane, and choose to show the Virtual Machines)
  2. Add the vCenter server.

vCenter Upgrade/Replacement: When deploying a replacement vCenter, please follow VMWare's specific processes to complete a "migration."
Upgrading vCenter Server Appliance 5.0.x/5.1 to 5.5 (2058441)​
Best practices for upgrading to vCenter Server 6.5 (2147686)
Best practices for upgrading to vCenter Server 6.7 (54008)​

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section