vRealize Automation three-node appliance topology does not come online correctly during a disaster recovery failover operation

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:
During a disaster recovery failover operation of vRealize Automation with Site Recovery Manager, the three-node vRealize Automation cluster does not come online.

Environment

VMware Validated Design for Software-Defined Data Center (SDDC)
VMware Validated Design for Software-Defined Data Center (SDDC) 5.0.x
VMware Validated Design for Software-Defined Data Center (SDDC) 4.3.x
VMware Validated Design for Software-Defined Data Center (SDDC) 5.1.x

Cause

As of VMware Validated Design for Software-Defined Data Center 4.3, vRealize Automation uses a three-node topology for the virtual appliances. The primary node should be the first node that is powered on for the vRealize Automation appliances. It is not always possible to determine which appliance is running as the primary node as the primary role may have failed over to another appliance before the disaster recovery operation.

Resolution

Modify the Cloud Management Recovery Plan to ensure the 01a node (e.g. vra01svr01a) is powered on first.

1. In the vSphere Client or the vSphere Web Client, click Site Recovery > Open Site Recovery.
2. On the Site Recovery home tab, select a site pair and click View Details.
3. Select the Recovery Plans tab, right-click a recovery plan, and select Edit Plan.
4. Move vra01svr01a into the priority 1 group with the vRealize Automation IaaS SQL Server.
5. Insert a break point (User prompt) in the recovery plan after priority 1 VMs
6. Insert a break point (User prompt) in the recovery plan after priority 2 VMs

The recovery plan will pause after the priority 1 group has started

1. Prompt user to do the following:
   1. Log into https://vra01svr01a.rainpole.local:5480.
   2. Navigate to the Cluster Tab. (in vRA version 7.4 this setting is under vRA settings -> Database)
   3. Review the Type & State of vra01svr01a.
2. If Type = PRIMARY
   1. Change the Database Mode to Async.
   2. Resume the recovery plan powering on the priority 2 group.*
   3. Review the Type & State of vra01svr01b & vra01svr01c once powered on.
   4. If State = NA/NA or Up/NA
      1. Click Reset on vra01svr01b followed by Reset on vra01svr01c.
   5. Change the Database Mode to Sync.
   6. Resume the remainder of the Recovery Plan.
3. If Type != PRIMARY
   1. Click Promote and wait until promotion completes.
   2. Change the Database Mode to Async.
   3. Resume the recovery plan powering on the priority 2 group. *
   4. Review Type & State of vra01svr01b & vra01svr01c once powered on.
   5. If State = NA/NA or Up/NA
      1. Click Reset on vra01svr01b followed by Reset on vra01svr01c.
   6. Change the Database Mode to Sync.
   7.  Resume the remainder of the Recovery Plan.

* Note: The Recovery plan will pause after the priority 2 group has started