Skip to main content


Druva Documentation

About recovery workflow

Phoenix Editions: File:/cross.pngBusiness         File:/tick.png Enterprise     File:/tick.pngElite
(Purchase Separately)

Phoenix DRaaS provides advanced orchestration capabilities to achieve greater control of the failover of virtual machines in the production and test environments. The Recovery Workflow enables you to define steps to logically group virtual machines in a DR plan to perform operations in a defined order. You can add multiple steps, such as virtual machine (VM) boots and time delays, to the recovery workflow of your DR plan. For example, you can group specific virtual machines in a single VM boot step and specify their boot order, and add scripts in the recovery path to perform critical operations. You can also define a time delay step between the execution of the two steps during the recovery operation.

When you create a DR plan, Phoenix creates a default recovery workflow for the DR plan and adds all the virtual machines in the DR plan to a single VM boot step. The Recovery Workflow section on the Recovery tab lists the default recovery workflow. You can edit the default recovery workflow based on your failover requirements by adding multiple steps containing virtual machines. You can add post-boot scripts to virtual machines to execute specific commands during the failover operation. For example, you can add a script to a critical virtual machine to verify the successful boot of the failover instance and based on the script result, you may continue with the failover operation.  You can also add scripts to change hostnames of the EC2 instances, modify service configurations, add or remove network routes and gateways, and so on. 

For more information about how to edit a recovery workflow, see Edit failover recovery workflow.

  • Was this article helpful?