vRealize Suite 2017 Disaster Recovery by Using Site Recovery Manager 8.1 describes how to implement and use Site Recovery Manager with vSphere Replication or array-based replication to protect the vRealize Suite components.

The following vRealize Suite components were tested for disaster recovery by using Site Recovery Manager 8.1:

  • vRealize Automation 7.0.1 and later

    • vRealize CloudClient 4.1 and later

  • vRealize Orchestrator 7.0.1 and later

  • vRealize Operations Manager 6.3.0 and later upto 6.7


    vRealize Operations Manager disaster recovery was tested completely with vSphere Replication. However, vRealize Operations Manager disaster recovery was tested with the array-based replication in a limited manner, only by using EMC RecoverPoint.

    • vRealize Operations Manager 6.3 only supports up to Site Recovery Manager 6.1

    • vRealize Operations Manager 6.3.1 supports up to Site Recovery Manager 6.5

    • vRealize Operations Manager 6.5.x supports up to Site Recovery Manager 8.1

  • vRealize Log Insight 3.3.0 and later

The following products were used for implementing disaster recovery for vRealize Suite:

  • VMware vSphere Replication 6.0

  • Array-based replication

    • EMC RecoverPoint Storage Replication Adapter

    • vCenter 6.0

For information about installing, upgrading, and configuring VMware Site Recovery Manager, see the VMware Site Recovery Manager 8.1 Documentation.

To protect the vRealize Suite components, you must configure the Site Recovery Manager tool and the vRealize Suite components in the following order:

  1. Configuring Site Recovery Manager. You must configure Site Recovery Manager by following the guidelines to protect your vRealize Suite components.

  2. Configuring vRealize Suite Components for Disaster Recovery. You must configure the vRealize Suite components that you want to protect by using Site Recovery Manager.

  3. Testing and Executing a Recovery Plan. You must test the recovery plans that you have created to verify that the recovery is successfully completed without any data loss, before a disaster recovery situation occurs.