After recovery of vRealize Automation by using Site Recovery Manager is completed, depending on the scenario, you should complete some post-recovery steps.

Depending on what components of vRealize Automation system you want to protect, you must follow one of the following scenarios.

Scenario 1 - vRealize Automation Components Only

When you plan to protect the vRealize Automation components only, after recovery is completed, the vRealize Automation components are turned off. You must start up the vRealize Automation components in a specific order. The vRealize Automation components are by default turned on by the Site Recovery Manager recovery plan. The order of starting the components can be configured by using the power-on Site Recovery Manager groups. For more information on the start up order, see Start Up vRealize Automation.

Scenario 2 - vRealize Automation Managed VMs Only

If you plan to protect vRealize Automation managed VMs only, after recovery is completed, you do not have to perform any additional steps. You should make sure that vRealize Automation and its components are up and running before executing recovery for the managed VMs.

CloudClient supports automatic import of the managed virtual machines, however if you want to manually import the managed virtual machines, see Bulk Import, Update, or Migrate Virtual Machines.

Scenario 3 - vRealize Automation Components and Managed VMs

When you plan to protect vRealize Automation components and managed VMs, after recovery is completed, the vRealize Automation components are turned off. You must start up the vRealize Automation components in a specific order. For more information on the start up order, see Start Up vRealize Automation. If you plan to protect vRealize Automation components and managed VMs together, you may need one or more Site Recovery Manager depending on the number of protected VMs. You can select one of the following options to successfully run and complete recovery for vRealize Automation components and the managed VMs.

Note:

You can protect up to 5,000 VMs on single Site Recovery Manager.

  • If vRealize Automation components and managed VMs are protected by using only one Site Recovery Manager, you can run the recovery for the vRealize Automation components and managed VMs together. No additional considerations are required.

  • If you have vRealize Automation components and managed VMs on a single Site Recovery Manager and more managed VMs on any additional Site Recovery Manager, ensure that the recovery for Site Recovery Manager with vRealize Automation components is executed and vRealize Automation is up and running, before you run any Site Recovery Manager with managed VMs. You can execute recovery for managed VMs on remaining Site Recovery Manager simultaneously or in any order.

  • If you have vRealize Automation components on one Site Recovery Manager and managed VMs on two or more Site Recovery Manager, ensure that the recovery for Site Recovery Manager with vRealize Automation is executed and vRealize Automation is up and running, before you run any Site Recovery Manager with managed VMs. You can execute recovery for managed VMs on multiple Site Recovery Manager simultaneously or in any order.

CloudClient supports automatic import of the managed virtual machines, however if you want to manually import the managed virtual machines, see Bulk Import, Update, or Migrate Virtual Machines.