StarWind Software

Hello all and Happy New Year!
I am not sure if the Synchronization feature to capture 'live' changes of the running source VM is a newer feature or not, but I may have arbitrarily enabled this option during the setup process of the latest V2V I'm running.
I am running this conversion on a 1GB network for a basic file server, total data disk size is only about 650GB of used storage.
The initial image conversion finished after 3 days or so- now I am seeing the "synchronization image" task running which by my calculations will take another day and a half or so.

I know hardware / network / resource restraints are slowing this down, but for a file server like this, it would be faster to have just captured the initial image and then used a tool like BeyondCompare to capture any recent changes (which given the holidays there are very few recent changes, so I can't imagine the snapshot would grown hardly at all).
Ideally we'd have a 10GB network in place, but alas we don't.
The sync image is at 20% after about 12 hours- would cancelling it corrupt the converted virtual disk? It just doesn't seem to be worth the time in this case to capture next to nochanges on the image synchronization.
Thank you for any feedback!

Please don't cancel as there is a snapshot merge in process.
Since the conversion is live, you can continue using your systems.

I did some experimenting- on the HV host where the virtual disks are being transferred to, the vhdx files are not locked, I was able to copy them while the delta sync was occurring.

The data disk appears to be mountable, but the OS disk was not bootable, I imagine because one of the final steps the V2V converter does is to fix the bootability.
Delta sync is still in progress but I do have a usable data disk.

That's because of drivers. The VM does not "like" the destination. The problem might be fixed by removing VMware tools before the conversion.
Also, you can try the IDE controller and VHD device instead.
Good luck with your project.

Canceling the synchronization phase should not corrupt the already converted virtual disk, but you will lose any changes made on the source VM after the initial image capture, so it’s generally safe if minimal changes occurred and you’re prepared to handle them manually.

I won't be so certain, as you are dealing with the snapshots.