Keep track of VMs during infrastructure changes

[zahradnik]

I've separated backup network based on Best practices. Which means I had to change all ESXi hosts (different subnet, different IP address) linked to Veeam. Changing hosts means changing all backuped VMs. Please consider detecting that added VM to the backup job has the same unique identifier in source system (vSphere) and perform incremental update as no change happened. Now I have 10x bigger daily incremental backup which significantly filled up backup storage and my uplink to DR site has been saturated for few days.

[PTide]

Hi,

Normally VMs' morefIDs are not changed as long as the corresponding ESXis stay under the same vCenter which has been used to add the VMs into backup jobs. If you ended up in a situation when all your VMs' IDs have changed but the VMs' names stayed intact, you can use this tool to remap things back into business.

Thanks!