VMware Validated Design 4.2 vRealize Operations Disaster Recovery Failover and Failback
search cancel

VMware Validated Design 4.2 vRealize Operations Disaster Recovery Failover and Failback

book

Article ID: 319652

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article provides recommend steps to perform a disaster recovery failover and failback of vRealize Operations from when vRealize Operations Manager remote collectors are inaccessible.

Environment

VMware Validated Design for Software-Defined Data Center (SDDC) 4.2.x
VMware Validated Design for Software-Defined Data Center (SDDC)

Resolution

Note: The FQDNs and node names below are examples.  Replace the FQDNs and IPs as needed.

After you perform disaster recovery, when vRealize Operations Manager remote collectors in Region A are permanently inaccessible, you remove the remote collectors from vRealize Operation using the administrative UI.

Failover to Region B:
In the event of a site failure in Region A, after performing Disaster Recovery of the Operations Management Applications in Region B, when remote collectors of vRealize Operations Manager in region A are permanently inaccessible, you remove and redeploy the remote collectors from vRealize Operation using the administrative UI.

Perform the following steps as part of Post-Failover Configuration of the SDDC Management Applications:
 

Delete the inaccessible remote collectors from vRealize Operations administration UI and vSphere inventory

  1. Log in to vRealize Operations Manager Primary Node's admin UI at https://vrops01svr01a.rainpole.local/admin as the local admin user.
  2. Select the sfo01vrops01a remote collector and click Remove Node.
  3. Check I understand that performing this action will remove the selected Node from the Cluster and click Yes.
  4. Repeat steps 2-3 for the sfo01vrops01b remote collector.
 

Redeploy and connect the remote collectors after the cluster is moved back to Region A as part of failback after Region A restoration:

  1. Log in to the vSphere Web Client at https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client as [email protected].
  2. From the Home menu, select VMs and Templates.
  3. Navigate to the sfo01m01vc01.sfo01.rainpole.local vCenter Server and expand the sfo01-m01dc data center.
  4. Click the virtual machines tab.
  5. Right-click sfo01vrops01a, select Delete from disk and click Yes to confirm the deletion.
  6. Repeat the above step for sfo01vrops01b remote collector.
  7. Follow Deploy the Remote Collector Virtual Appliances in Region A to redeploy the remote collectors.
  8. Follow Connect the Remote Collector Nodes to the Analytics Cluster in Region A to connect the remote collectors to the cluster.
  9. Log in to vRealize Operations Manager Primary Node's admin UI at https://vrops01svr01a.rainpole.local/admin as the local admin user.
  10. Click the Finish Adding new nodes option under Cluster Status.
 

Reset the collector group

  1. Log in to vRealize Operations Manager Primary Node's admin UI at https://vrops01svr01a.rainpole.local/admin as the local admin user.
  2. Navigate to Administration > Management > Collector Groups.
  3. Select sfo01-remote-collectors and click Edit.
  4. Select sfo01vrops01a and sfo01vrops01b and click Save.