The Migration interface includes an option for canceling in-progress migrations.
For OSAM, the effect of canceling a migration depends on the state of the migration when selecting the Cancel option:
Canceling a migration while an HCX appliance is replicating data to the destination site deletes the associated resources created at the destination site with no effect on the source VM.
Canceling a migration when the source system is in the final sync phase reboots the source system and deletes the associated resources.
Canceling a migration after the target VM has been created deletes the destination virtual machine and the associated resources.
Canceling a migration after the source virtual machine is powered down requires you to restart the virtual machine at the source site. HCX deletes the associated resources at the destination site.
For RAV, vMotion and Cold migration, you can cancel a migration at any point and the source VMs retain their original state.
For Bulk migration, the replication is canceled on the source site VM, and replicated data is deleted from the destination site. Canceling a migration after the target virtual machine is powered on prevents the source virtual machine from returning to a powered-on state. Ensuring only one instance of a virtual machine is powered on prevents duplicate active instances of a virtual machine on both the source and the destination sites.
If Seed Checkpoint is enabled for RAV or Bulk migration, HCX retains any transfered data at the destination site.
