Host-based backup of VMware vSphere VMs.
Post Reply
yzfr6
Influencer
Posts: 19
Liked: 2 times
Joined: Nov 21, 2011 8:20 pm
Full Name: Chris
Contact:

Backup footprint after migrating from VMFS to VVOLs

Post by yzfr6 »

I have a customer that is planning on migrating from VMFS datastores to VVOLs. Currently they are backing up with Veeam to a local REFS repository on the Veeam server. Once the VMs are migrated to VVOLs, will Veeam see them as "new" and have to do a full backups of the VMs requiring the additional storage capacity to hold the "new" VMs along with the old backups for retention? or will Veeam continue on like nothing has changed?
PetrM
Veeam Software
Posts: 3229
Liked: 520 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Backup footprint after migrating from VMFS to VVOLs

Post by PetrM »

Hi Chris,

Full run will be triggered if VM reference (also known just as MoRef ID) is changed at the level of vCenter, for example when you re-register VM in vSphere client.
I don't see any reason why MoRef ID could be changed due to VM migration from one datastore to another, so I would expect normal incremental run according to job schedule.

On the other hand, it always makes sense to test migration scenarios before applying them to real production workloads: make full backup of test VM residing on VMFS, then migrate it to VVOL,
then run job once again.

Thanks!
Post Reply

Who is online

Users browsing this forum: Google [Bot], Semrush [Bot], SysSadMan and 74 guests