Discussions specific to the Microsoft Hyper-V hypervisor
elsispro
Lurker
Posts: 1
Liked: never
Joined: May 16, 2019 11:44 am
Contact:

[MERGED] Moving VMs to another host

Post by elsispro »

Is there a way to make VBR be aware of the VM being moved from one standalone Hyper-V host to another and continue the backup chain instead of creating a new chain? For example If I have one job that has multiple Hyper-V hosts added (that is - all possible VMs) and I move some VM from one host to another (even preserving the name and ID of VM) VBR does not continue the original chain, but create a new one instead. This is very inconvenient if there are frequent VM moves. And you cannot delete the old chain right away, because you would lose previous restore points.

Vitaliy S.
Product Manager
Posts: 25035
Liked: 2133 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Moving Hyper-V guest VM to another host

Post by Vitaliy S. »

If you're using Failover Cluster or SCVMM as a root object in the backup inventory (jobs), then migrating VMs between hosts should not cause this behavior. Please review this thread for more information. Thanks!

willrussell
Service Provider
Posts: 24
Liked: 11 times
Joined: Nov 23, 2017 5:05 pm
Contact:

Re: Moving Hyper-V guest VM to another host

Post by willrussell »

mkaec wrote: May 14, 2019 1:17 pm Mike,

It would actually be possible to do for the normal case. The VM GUID does not change when the VM is moved (at least on Hyper-V). B&R currently maps the VMs based on both the GUID of the host and the VM. Logic could be implemented that if a VM is missing from a backup job, to see if the missing GUID is now present on another host and automatically link it back up. This would work 99% of the time, but I understand if you wouldn't want to implement something that is not 100%.

However, what your standalone host users could use is a mapping tool that would allow an administrator to tell B&R where a VM has been moved to, just like there is for telling B&R where backup files have moved to. This would be a suitable solution for the standalone host users. They typically don't move VMs that often, but when they do it is unpleasant to have to restart the backup chain over again.
Mike Resseler wrote: May 15, 2019 6:11 am Hmmm. That might be something to consider. Fact will remain that it will be a full backup on everything pre-2016 because we lost the incremental knowledge there.
Mike,

Was this ever actually considered as an improvement?

We've got a few clients who have only two Hyper-V hosts but no shared storage or VMM server. If we could have a manual mapping tool to tell B&R it's the same VM on the new host that would be very helpful in terms of saving backup storage space.

Will

Vitaliy S.
Product Manager
Posts: 25035
Liked: 2133 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Moving Hyper-V guest VM to another host

Post by Vitaliy S. »

If you're using the reversed incremental mode, then you could use a backup mapping option in the job settings. This option will still create a new full backup, but it will not consume 2x space since you already have a full image stored on the VBK file (latest file). If you're using forward incremental mode, then there are no changes in how Veeam B&R behaves when VMs are migrated from host to host without using Failover Cluster/SCVMM. Thanks!

willrussell
Service Provider
Posts: 24
Liked: 11 times
Joined: Nov 23, 2017 5:05 pm
Contact:

Re: Moving Hyper-V guest VM to another host

Post by willrussell » 1 person likes this post

Hi Vitaly,

Thanks for the clarification, that's useful to know.

Will

mkaec
Expert
Posts: 367
Liked: 93 times
Joined: Jul 16, 2015 1:31 pm
Full Name: Marc K
Contact:

Re: Moving Hyper-V guest VM to another host

Post by mkaec »

I was excited to be notified there was a response in this thread, but sad to find that there is still no plan to ease the pain for customers that move VMs on standalone Hyper-V hosts that don't have SCVMM.

dmitryk8
Novice
Posts: 7
Liked: never
Joined: Apr 01, 2019 7:30 am
Full Name: Dmitriy
Contact:

Re: Moving Hyper-V guest VM to another host

Post by dmitryk8 »

I need to move some VMs from one Hyper-V cluster to another. Current VBR build is 10.0.0.4461 P1.
As I understand, the only way is to remove VM from the job and then add again? Or may be there were improvements?

Egor Yakovlev
Veeam Software
Posts: 2120
Liked: 524 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Moving Hyper-V guest VM to another host

Post by Egor Yakovlev »

No improvements.
Moved VM receives a new ID at the target host\cluster and is treated as new VM by Veeam respectfully. Re-add is still the way to go, and if mass VM migration is planned, a PowerShell script might ease your migration process with jobs edit.
/Cheers!

mkaec
Expert
Posts: 367
Liked: 93 times
Joined: Jul 16, 2015 1:31 pm
Full Name: Marc K
Contact:

Re: Moving Hyper-V guest VM to another host

Post by mkaec »

And "Map" functionality that would ease the process after the move is still MIA.

Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests