Discussions specific to the VMware vSphere hypervisor
We have to v2v one of the largest machines. From what i have seen with veeam 8 is that if the vmware id changes, the machine is seen as new machine.
How to prevent this?
- Veeam Software
- Posts: 20535
- Liked: 1973 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
There's currently no way to avoid this, besides editing Veeam database to match the IDs, which we do not recommend to do without support assistance.
We have full support so one phonecall/rss would solve this?
- SVP, Product Management
- Posts: 29372
- Liked: 5486 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
If you actually V2V the machine, you have to start backing it up from scratch as the new machine, instead of attempting to match the ID (even with a help of support). Matching can only be done when the only thing that changes about a VM is moRef ID (but actual VM remains exactly the same). Thanks.
V2V is still the same machine, a few thinks change that is true. The only reson is because someone had thin disks in mind while it has to be thick.
So essentially the machine stays the same and the old one isn't comming back, only the disk will be thick and not thin. But even then it is a new machine for veeam?
What would be the best way to update the target after the v2v?
- Veeam Software
- Posts: 6039
- Liked: 1843 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
Yes, we refer to VMware MorefID to identify VMs, it's the only stable and guaranteed method.
Even if the VM will be marked as a new one, most of the blocks of the VM itself will be inside the existing job, so I'm expecting anyway a new run of the backup to deduplicate a lot thanks to existing blocks. Maybe you can simply let the job run and see if the deduplication ratios will be good anyway...
Also, honestly I don't see thin/thick disks to affect block changes to be honest.
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2021
Veeam VMCE #1
Well, done the big step this year. It took Veeam just 2 and a half days to replicate the V2V machine using all bandwith available during those days. In my humble knowledge, that's a full replication job without the use of any of the off-site dedupe blocks. The whole machine should have been in the cache (see my post about wan accelerator cache usage) sinds the V2V machine is exactly the same as the original.
Don't know if that is working as designed or not.