Vmware VM Migration and Veeam mapping

[rosmith42]

We have Production and test resource pools in our Vmware infra.

My question is this....Since two of our Vms are no longer Test VMs and now in Production, what is the best way to migrate Vms to another resource pool and still have the backups in the previous pool backed up without starting a new backup? It seems that once I have already moved and "migrated" the Vms to another datastore, the previous backups sitting on the Exagrid repository also need to move. Should I have used "Quick Migration" in Veeam instead? Would this have moved the existing backups from the one repository to another? I'm aware of the map option but it's only two VMs I've moved and not a whole resource pool. I haven't done this before and I'm not sure if Veeam is smart enough to know that the 2 Vms are now in a different pool.]Suggestions?

[DGrinev]

Hey,

Are you managing VMware infrastructure through the vCenter?

[rosmith42]

Yes. I am.

[DGrinev]

Migration within the same vCenter doesn't break your backup jobs, since all VMs will preserve its morefIDs. Thanks!

[rosmith42]

Well, the issue is when the new job runs tonight, it will "not" see the previous existing backups so it will make a new backup based on the new resource pool that it is in now (Migrated from Test resource pool to Production app pool). Is there a way to move the pre-existing VM backups from test to prod, not the VMs themselves? Vmware doesn't care about the fact they got moved but Veeam will not know the backups already exist so it will make a new backup. I hope I am being clear on this.

[foggy]

So they will be backed up by another job - in this case you can copy the backups to another folder/repository and map the new job to them. Are you using per-VM backup chains?

[rosmith42]

Yes the backup jobs are using Per Vm backup chains.

[foggy]

Then just copy the corresponding backup files along with VBM file for this job to a new folder, rescan it, map the job and clean-up missing restore points.