vRealize Orchestrator Disaster Recovery

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

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

1. vRealize Orchestrator is embedded in vRealize Automation: The disaster recovery information for vRealize Automation applies to an embedded vRealize Orchestrator.
2. vRealize Orchestrator is used as a standalone virtual appliance: You should restart the vRealize Orchestrator appliance after a recovery plan is executed. There are no additional disaster recovery guidelines for a standalone vRealize Orchestrator virtual appliance.
3. vRealize Orchestrator is used as a Windows installable: You should restart the vRealize 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:

• Validating Workflows
• Debugging Workflows
• Running Workflows
• Resuming a Failed Workflow Run

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 vRealize 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.