So, I've some rather big NFS servers with a some TBs of data sitting in some VMDKs.
To upgrade to the latest version of the O/S with little downtime, we've spun up a new virtual machine and plan to attach the data VMDKs of the old VM to the new VM.
My question is, how does Veeam handle this? Is the disks CBT data valid and honored, will it do an Active Full and if so, if we use the same backup repository for the new VM as for the old VM, there should be little to no additional backup space required, right?
Thanks everybody!
-
- Enthusiast
- Posts: 51
- Liked: 10 times
- Joined: Apr 17, 2014 8:25 am
- Full Name: Jens Siegmann
- Contact:
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: How does Veeam behave when VMDKs are moved to other VMs?
A new VM having old data disks attached to it will be backed up in a full mode.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: How does Veeam behave when VMDKs are moved to other VMs?
If you're using reversed incremental backup mode, then deduplication should save you some space due to old and new full VM backups being stored in the same VBK file.
Who is online
Users browsing this forum: Google [Bot] and 22 guests