V2V - Warm Migration Controlling Final Shutdown

[tsukraw]

Hey guys,

We are ramping up our VMware to Vates migrations.

One item that has come up is we would like to be able to use the Warm Migration method mentioned here: https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/

The feedback I have got from our guys is that once you start the warm migration you really lose control. What I mean by this is on the final snapshot, shutdown of the VMware side. This happens when the initial copy is completed.

Without having some form of control, the options cannot be leveraged properly as the shutdown could happen mid-day when the server is being utilized.

Is there possibly via CLI any way to control the final step?
It would be really nice if the final step did not happen automatically, and once the initial sync is completed we had a button or such to trigger final sync and shutdown. That way we could arrange for it to happen after hours.

Just an idea if there is no way from CLI.

Thanks

[olivierlambert]

Hi,

Question for @florent

[florent]

@tsukraw yes it is already possible , and there is even a documentation : https://docs.xen-orchestra.com/v2v-migration-guide#-final-migration

works the same through xo-cli ,or through the UI. You'll need to keep the same storage/template for both migraiton, don't create new snapshot on the vmware side, and it can only works if warm migration works

[tsukraw]

@florent

I have read through the guide you have provided but I'm struggling with it.

The guide does not appear to be a full sync and then a delta sync.
The guide appears to be for a per-migration test, which you then delete the test sync and re-run a migration.

This is the step that seems to suggest this:
"Remove the test copy
Once you’ve finished your checks and taken notes, delete the test VM. This will free up resources and prevent any confusion before the final migration."