Disaster Recovery and DR Preparedness : (Workflow) Fail over HA to DR Appliance
  
(Workflow) Fail over HA to DR Appliance
Use this procedure, in conjunction with your business continuity plan, in the event of a site disaster at the HA site or if you’ve experienced an onQ Appliance failure. The following table lists some of the most common failure scenarios. The table also discusses seeding; for information the seeding process, go to Seed the DR Repository.
Failure Scenario
Disaster Recovery (DR) Solution
 
DRaaS (Hybrid Cloud)
onQ Appliance (on‑Premises)
Hardware component failure on HA
Run DR Appliance in HA role while Quorum replaces the FRU, or sells/loans you an HA replacement, followed by a pre‑seeded box to synchronize the onQ Appliances.
Run DR Appliance in HA role, Quorum can employ one the following solutions:
Replace the FRU (Field Replaceable Unit) on HA.
Sell/loan you an HA replacement, followed by a seed box for the DR site, if WAN synchronization isn’t possible, to synchronize the onQ Appliances.
Moves the DR to the HA site, then proceed with seeding.
Site power outage at HA site
Request that Quorum Support run DR in HA role while you fix the power outage. Afterward, Quorum can loan you a pre‑seeded box to synchronize the onQ Appliances.
Run DR Appliance in HA role while you fix the power outage. Afterward, Quorum can loan you a seed box if WAN synchronization isn’t possible for the DR site, to synchronize the onQ Appliances.
Software corruption on HA
Request that Quorum Support run DR in HA role while Quorum reimages/rebuilds the HA. Afterward, Quorum can loan you a pre‑seeded box to synchronize the onQ Appliances.
Run DR Appliance in HA role while Quorum reimages/rebuilds the HA. Afterward, Quorum can loan you a seed box for the DR site, if WAN synchronization isn’t possible, to synchronize the onQ Appliances.
Only an HA (local) can back up recovery nodes. Because your HA is unavailable, the DR Appliance (remote), whether DRaaS or on‑premises, must take on this role; otherwise, your recovery nodes, which are now acting as the protected nodes, will not be backed up.
Therefore, a failover involves the DR Appliance taking on the HA role and running the recovery nodes.
As soon as your HA/local site is available, you must fail back.
To fail over to remote onQ Appliance:
1. Ensure that the local onQ Appliance is down (powered off) or that protection is off.
When an onQ Appliance boots, protection is automatically off. Protection on an HA instructs the HA to perform backups. Given that the HA (local) still has its role set to HA, protection on that HA must be off until the failback completes.
2. Log on to the DR Appliance’s onQ Portal.
3. Start all the recovery nodes on the DR Appliance (remote onQ Appliance). The boot order must take into account any interdependencies.
4. If applicable, restore the Oracle database:
Back up and restore Oracle 11g database on Linux
Back up and restore Oracle 10g+ database on Windows
5. Add a host entry for each protected node, if you haven’t already done so.
6. Change the DR Appliance’s role to HA.
The recovery nodes on the remote onQ Appliance become the protected nodes; the remote onQ Appliance backs up these recovery nodes.
7. Establish a secure connection between the RNs and the DR Appliance. Go to Create secure connection to PNs.