Moving vms to new physical location

[jrbaumann]

Hello,

We are currently moving vms from one physical location (City A) to another physical location (City B) with Zerto. We are still performing backups on the vms with Veeam, the current backups are stored in City B while the vms reside in City A. Once these are replicated over to City B, do we need to reconfigure the backups and start a new chain on the moved vms as they have already been backing up to City B?

The migration of servers started before i came on board.

Thanks

JB

[Rick.Vanover]

Are they VMware VMs? If so, next question is if it is the same vCenter in city A and city B? If yes to the vCenter being the same, would the VM in site A be the same objection site B? You also could have done this with Veeam Backup & Replication the replication failover

Let's answer these questions first.

[veremin]

Once migration is over, you will need to reconfigure existing backups jobs (selecting VMs from host B as new job source). However, subsequent cycle will be a full one, as those VMs will be considered as completely new ones. Thanks!

[jrbaumann]

Thanks for the quick reply!

@Rick - yes the vms are vmware and will be in the same vCenter and not sure what you mean by same objection site B - not sure why they chose Zerto to do the migration, but we won't be keeping the current vms, just the replicated ones eventually.

@Vladimir - Ok, so that means we should see 2 vm backup chains under Backups\Disk\Job Name with the same name being backed up to the same repository? Remember we are currently backing the old server up to the same place as the new ones will be. We will need to disable the backup job at the old and start a new chain, would be nice to just continue the current chain. We are backing up to Exadrid boxes.

Maybe i'm not understanding totally.

[Rick.Vanover]

Same object in Site B. Sorry - using speech recognition post shoulder surgery.

But worst case is VM considered new VM as Vova indicates, really - worst case - it's an active full, so IMHO not a big deal. If you are concerned about the timing - you can stagger them to run the new full backups in site b.

[veremin]

The current chain will be continued, but a first backup cycle after migration will be full one. That's because migrated VM will have a different identifier and thus will be considered as new one from backup server perspective. Thanks!

[jrbaumann]

OK,

Great! Thanks for the replies and good luck on the rehab Rick!