You can use the following information specific to disaster recovery for Automation Orchestrator.

Note:

Disaster-recovery scenarios are not supported by Automation Orchestrator 8.0. Performing the disaster-recovery procedure might result in a non-functional Automation Orchestrator environment. The latest supported version of Automation Orchestratoris 7.6 and all 7.6 hotfix releases.

You may have Automation Orchestrator configuration available to you in one of the following way:

  1. Automation Orchestrator is embedded in VMware Aria Automation: The disaster recovery information for VMware Aria Automation applies to an embedded Automation Orchestrator.

  2. Automation Orchestrator is used as a standalone virtual appliance: You should restart the Automation Orchestrator appliance after a recovery plan is executed. There are no additional disaster recovery guidelines for a standalone Automation Orchestrator virtual appliance.

  3. Automation Orchestrator is used as a Windows installable: You should restart the Automation Orchestrator services on the Windows VM after a recovery plan is executed.

You should manually validate the status of all the workflows that were running during the event. For more information on how to validate, debug, run, and resume workflows, refer to:

If you have an external MS SQL database, you should protect the VM that contains the MS SQL database by using Site Recovery Manager. If the MS SQL database VM that is associated with Automation Orchestrator contains other databases, keep in mind that these databases may be affected at the time of recovery and plan to protect these databases as per your site policy.