Best Practice when moving a VSA based VM to a different virtual center?

Question

We are retiring a VMware DC and the admins are moving the VMs from the original vCenter to a completely different vCenter. I believe they are cloning them but not 100% sure. Anyway, we have been removing the VM from it’s original user defined subclient in vCenter X and adding it to a new subclient in vCenter Y. The VM name and vc.uuid has not changed. I noticed when we do this we now show two defaultBackupSet’s under the clients VMInstance - defaultBackupSet and defaultBackupSet_Vir-NewOne. After 7 days, we start getting alerts that the VM hasn’t been backed up in 7 days under the old VC and subclient. Trying to understand why CV is doing this and if this is fine or should we be moving these differently? And why, if the VM no longer is in the old subclient would CV thinks it should still be getting backed up thru it. Thanks.

Best answer by Sureshkumar S

Hi @SCI85_BJC ,

Good day!

The VM's are discovered using the UUID . if the UUID is same you will see 2 backupset on the same virtual machine.

As there will be still valid backups on the old Vcenter you may get alerts on the VM. You can exclude the Vm from alert using filter or association in the alert

Once that old VC client backups expired and client is retired you wont see this alerts

Regards,

Sureshkumar S

Sureshkumar S · Accepted Answer

Hi ​@SCI85_BJC,Good day!The VM's are discovered using the UUID . if the UUID issame you will see 2 backupset on the same virtual machine.As there will be still valid backups on the old Vcenter you may get alerts on the VM. You can exclude the Vmfrom alert using filter or association in the alertOnce that old VC client backups expired and client is retired you wont see this alertsRegards,Sureshkumar S

Sureshkumar S · Answer

Hi ​@SCI85_BJC,Yes once data is aged off you can remove that backupset or old vcenter itself.Regards,Sureshkumar S

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded