V2V for large VMs, how to maintain consistency

[afb.nfz]

hi i'm trying to move a handful of VMs from a 2012R2 Hyper-V environment to a 2022 Hyper-V. StarWind V2V seems to work flawlessly, but i've only tested it on a VM with smaller (~100GB) disks.

A few of the VMs i need to migrate have 2-5TB of VHDs, and for various reasons i only have a 1Gbps connection between the hosts. So it's going to take a looooong time.

My question is, if this is snapshot-based replication, does V2V have the ability to do a 2nd incremental R/W to capture all the data that's changed on the source, between the initial snapshot and the time when the conversion is finished?

or is there another StarWind tool that DOES have this capability?

thanks

[yaroslav (staff)]

Sadly no. You need to keep the VM offline for the entire conversion time.
Why don't you just move the VM between the Hyper-V hosts via Hyper-V Move, update the VM version, and register the VM in place.

[herbertjones]

I think it's no.Your VM needs to be kept offline for the entire conversion period.

[anton (staff)]

We do (Hyper-V) or will do soon (VMware & KVM) "live" conversion when you don't need to shut down any VMs. FYI.

I think it's no.Your VM needs to be kept offline for the entire conversion period.