To migrate the virtual machines of VMware Aria Automation from the protected to the recovery VMware Cloud Foundation instance under planned circumstances, run the recovery plan for the cloud management applications in Site Recovery Manager.

Procedure

  1. Log in to Site Recovery Manager in the protected VMware Cloud Foundation instance at https://<srm_fqdn>/dr as [email protected].
  2. In the existing site pair, click View details.
  3. Click the Recovery plans tab and click the recovery plan for VMware Aria Automation according to your VMware Cloud Foundation Planning and Preparation Workbook.
  4. Click the Recovery steps tab and click Run.

    The Recovery wizard appears.

  5. On the Confirmation options page, configure these settings and click Next.

    Setting

    Value

    I understand that this process will permanently alter the virtual machines and infrastructure of both the protected and recovery datacenters.

    Selected

    Recovery type

    Planned migration
  6. To initiate the planned migration of VMware Aria Automation, on the Ready to complete page, click Finish.

    This operation takes several minutes to complete.

  7. When prompted, verify that the load balancer virtual server for VMware Aria Automation is available and responds to ping requests, and click Dismiss.

    If you failed over the NSX load balancer, the NSX load balancer is running in the recovery VMware Cloud Foundation instance. Otherwise, the NSX load balancer is still running in the protected VMware Cloud Foundation instance.

  8. When prompted, verify that the clustered Workspace ONE Access instance is available at https://clustered_workspace_one_access_fqdn/admin, and click Dismiss.
  9. On the Recovery steps tab, monitor the progress of the recovery plan until all recovery steps complete successfully.
  10. When all the recovered virtual machines are running, start the VMware Aria Automation services.
    1. Log in to the primary VMware Aria Automation node by using a Secure Shell (SSH) client at <aria_automation_primary_node_fqdn>:22 as root.
    2. Run the following commands.
      /opt/scripts/deploy.sh
kubectl get pods --all-namespaces

What to do next

  1. Verify that VMware Aria Automation is operational. See Operational Verification of Private Cloud Automation for VMware Cloud Foundation in the Private Cloud Automation for VMware Cloud Foundation validated solution.

  2. Prepare VMware Aria Automation for failback by reprotecting the virtual machines in Site Recovery Manager. See Reprotect VMware Aria Automationfor Site Protection and Disaster Recovery for VMware Cloud Foundation.