...
A single Avamar system is protecting multiple vCenter servers.When virtual machines are migrated between vCenters, the VMs are not dynamically vCenter domains in Avamar. After the vMotion, the VMs are displayed as "dimmed" in Avamar on the Source vCenter domain. The same VM is not dynamically added to the destination vCenter domain in Avamar. Forcing a vCenter synchronization fails to correct the virtual machines' status in Avamar.aa
In VMware, every virtual machine is assigned VC instance universally unique identifier (UUID). Avamar globally tracks virtual machines using this UUID. To prevent Avamar users from adding the same VM multiple times, Avamar's software will prevent a VM addition if the UUID is already associated with a existing client. This is true even when the virtual machines is inaccessible. When the VM is migrated from VC 1 to VC 2, the VM's UUID will disappear from the first VC 1, and appear in VC 2 at the VMware layer. Avamar will mark the client account in the client as (no longer addressable) in the virtual VC 1. The VM cannot be added to VC 2 as it is grayed out. For more information, see KB article 456087: Avamar - Cannot add a Virtual Machine to Avamar it is greyed out / grayed out If VC 2 is configured to automatically add VM (container client feature (avamar 7.0+ feature) or Auto-discovery feature (7.4+) ), mcserver.log.0 may record an error similar to this: WARNING: vCenter[vcenter.example.com] - Failed to register client Registrant -virtual_machine_name=vm1--domain=vcenter.example.com ......value="vm1""The vm is already a client."
Procedure: Upgrade to Avamar 7.5.1 or later which includes feature #273809. This feature allows the same UUID to exist in multiple vCenter domains if VM was added via Auto-Discovery feature. AND Enabled Rule based Auto-discovery feature using the same rule for both virtual center clients. Per the following snipet from the vmware guide: "In addition to auto-discovering new VMs, vMotion of VMs from one vCenter to another is also automatically detected by the Avamar software. If the new vCenter hosting the VM is configured in Avamar, the VM is automatically moved from the original vCenter client to the new vCenter client using the same user-defined rules to assign its domain and backup policy"
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.