HCX Migration Fails to Generate Migration ID After a Canceled Replication/Migration attempt

Products

• VMware HCX

Issue/Introduction

VMware HCX replication fails to transfer data for a configured virtual machine. After canceling the stalled migration and attempting to re-initiate the replication within a new Mobility Group, the system fails to assign a new Migration ID. The new Mobility Group remains in a Draft state.

In the HCX /common/logs/admin/app.log, an entry displaying the initial mobility group creation succeeding, but subsequent retry attempts show a null value for the migrationGroupId:

• [https-jsse-nio-<REDACTED_IPS>-8443-exec-5, Ent: HybridityAdmin, , TxId: TxId: <TX_ID>] INFO c.v.v.h.a.m.MobilityGroupRestController- Create mobility group request: class MobilityGroupRequest { items: [class MobilityGroup { name: <Mobility_Group_Name>-retry migrationWaveId: null migrationWaveName: null migrationGroupId: null

Environment

VMware HCX 4.11.3

Cause

The virtual machine is locked by a stale draft configuration from the previously canceled migration that was not fully cleared from the HCX Manager

Resolution

In the HCX Manager Connector appliance or where the Migration was configured from:

• Locate the previously canceled migration or the original Mobility Group in the HCX Manager.

• Execute the Force Cleanup action on the old migration, or entirely delete the previous Mobility Group.

• Verify that the cleanup process has successfully completed.

• Once the cleanup of the previous attempt is finished, navigate to the newly created Mobility Group.

• Validate and initiate the new migration to generate a fresh Migration ID and commence data replication.

Additional Information

Please reference the following KB article for Bulk Migration Best Practices

• HCX Bulk Migration operations and best practices

Please reference the following Techdoc articlew to cleanup Failed or Canceled Migration

• Force Cleanup for a Failed or Canceled Migration