Aria Automation does not update resource Cloud Account after Site Recovery Manager recovery plan execution & reprotection

Products

• VCF Automation

Issue/Introduction

After executing a recovery plan in Site Recovery Manager (SRM), Aria Automation fails to change the cloud account of the VM in its deployment.

This continues to show the source site of the SRM movement, indicating that Automation did not reconcile the migration.

More info is given on Automation reconciliation after SRM movement in TechDocs: Configure workload mobility in VMware Aria Automation

Environment

• VMware Aria Automation 8.18.1 (unpatched)
• VMware Aria Automation 8.18.1 patch 1-4
• VMware Site Recovery Manager

Cause

If you reprotect VMs in SRM before VMware Aria Automation has a chance to reconcile them to the new site, Automation may no longer recognize the source VM.
When a reprotection is performed in SRM, it changes the other-site VM to a placeholder in vSphere, which assigns it a new UUID and VC UUID. If the VM has not already been migrated by Automation, it is unable to identify this as the same machine.

Resolution

Preventative Measures: Before you reprotect VMs in SRM, perform one of the following actions to ensure synchronization:

• Allow 1 hour for the components to sync.

• Confirm in the GUI that the VMs have successfully changed their cloud account to the correct site in VMware Aria Automation.

 

Workaround for Affected VMs: If VMs have already been reprotected and failed to reconcile, contact Broadcom Support referencing this article (#439386)