(Workflow) Fail back DR to HA
You’ve been running your PNs on the DR Appliance; therefore, it has the most recent data. Now that you’ve either fixed or replaced the HA Appliance or the root cause of the site failure, use this procedure to synchronize the two onQ Appliances and fail back to the HA Appliance.
To fail back to local onQ Appliance:
1. Work with Quorum to determine the best option available to
synchronize the local onQ Appliance’s repository with the remote onQ Appliance’s repository, which has the most recent data.
Whether you have a Hybrid Cloud DR Appliance or on‑premises DR Appliance, if WAN synchronization is not practical, Quorum loans you a seed box; in the case of DRaaS, the seed box has your seed data pre-loaded. If you were sent a seed box, connect this NAS device to your network.
2. Schedule downtime based on the time needed to synchronize the repositories.
3. During the scheduled downtime (for estimates, go to
Seed the DR Repository), log on to the
remote onQ Appliance’s onQ Portal and do the following:
4. Power on the local onQ Appliance, if it isn’t already.
5. Change the local onQ Appliance’s
role to
HA, if it isn’t already.
6. Observe the repositories as they synchronize:
Whether you chose to use WAN synchronization or the seed box in
Step 1, that process takes place as soon as the local onQ Appliance boots up.
As the synchronization is in progress, proceed to
Step 7.
7. Log on to the
local onQ Appliance’s onQ Portal, and do the following to address failures to the protected nodes, if applicable.
a. Disable the protected nodes, so that the onQ Appliance does not perform backups during a restore.
c. Restore the protected nodes using one of the following methods:
8. On the
local onQ Appliance, bring up all the protected nodes. The boot order must take into account any
interdependencies.