Article number
000004668
Affected Versions
8.5
8.5 Update 1
Source Hypervisor
VMware
Target Hypervisor
VMware

Problem with vSphere Tags not Preserved After Recovering a VM

Viewed 287 times

Summary

Starting in Zerto 8.5, Zerto for vSphere customers can enable a feature that preserves the vSphere tags and category used by a production VM. This article reviews the reasons a tag and category would fail to be preserved and how to avoid these.

Root Cause

This issue can occur for any of the following reasons:

  • The setting "For incoming replication, copy the vSphere VM tags to the recovered VM" is not enabled at the target site.

  • The category used by the VM tag at the source site already exists at the target site, but the category properties does not include VM as an associable object type.

  • The VM was recovered using a Move operation.

  • The vSphere account that Zerto uses to access vCenter at the target site does not have the following privileges assigned: Assign or Unassign vSphere tag, Create vSphere Tag, Create vSphere Tag Category. 

Symptoms

After enabling the site setting "For incoming replication, copy the vSphere VM tags to the recovered VM", and conducting a recovery operation, the properties of the recovered VM do not include the vSphere tag and category.

The ZVM logs at the target site include an error similar to:

,VSphereTaggingService,AssignTagsToVM,Error occurred,"System.Exception Zerto.Zvm.Platform.VCenter.Clients.Rest.CategoryInfo CreateCategory(Zerto.Zvm.Platform.VCenter.Clients.Rest.TagCategorySpec) System.Exception: Exception of type 'System.Exception' was thrown.

Solution

To resolve this issue, kindly perform/confirm the steps below:

  1. Log on the the ZVM web UI, go to Site Settings - Policies, check the box next to "For incoming replication, copy the vSphere VM tags to the recovered VM", and save the change. The source site setting can be enabled to allow VM tags to be preserved upon failback.

  2. Edit the category in vSphere at the target site and add VM as an associable object type.

  3. Recover the VM using Live Failover instead of Move. The Move operation does not support the preservation of VM tags. Test Failover and Clone operations also preserve vSphere VM tags.

  4. Edit the vSphere account that Zerto uses to access vCenter at the target site and assign the following privileges: Assign or Unassign vSphere tag, Create vSphere Tag, Create vSphere Tag Category. Note: If two roles are assigned to a vSphere account, the role with the least privilege will apply. Review each role and verify the required privileges are assigned, or remove the account from a role that does not assign the required privileges.