HCX - VM instance UUID changes after vSR Bulk Migration performed to VMConAWS infra

Products

• VMware HCX
• VMware Cloud on AWS

Issue/Introduction

Detail the known scenario which leads to the instanceUUID (vCenter UUID) getting changed for VMs post vSR Bulk Migration workflow.

 

 

Symptoms:
A VM migrated to VMC on AWS SDDC will have the instanceUUID (same as vCenter UUID) updated after vSR Bulk Migration completion.

Cause

This issue is ONLY observed in VMConAWS infrastructure where "Register VM" call creates a new "instanceUUID" for the migrated VM on the target vCenter, even though there are no apparent instance UUID conflicts for existing VMs.
Note: It was very first observed during HCX Bulk migration(using vSphere Replication). But, it is also applicable to any workflow which uses vSphere Replication technology such as DR, SRM etc..

IMPORTANT: HCX RAV (Replication Assisted vMotion) also uses vSphere Replication technology but vMotion is used during switchover.

Resolution

None at the moment.

Workaround:
The RAV or vMotion migration profile can be used to migrate VMs to a VMC on AWS SDDC, if instanceUUID retention is required for the user.

Additional Information

Impact/Risks:

• The VM instanceUUID (vCenter UUID) will only change when migrated to a VMC on AWS SDDC using HCX vSR Bulk Migration.
• vSR Bulk Migration performed to other cloud infrastructures won't update VM instanceUUID.
• VM instanceUUID will be retained when migrated to ANY Cloud using RAV/vMotion migration types.