Skip to main content
Druva Documentation

About disaster recovery failover

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

In an event of an actual disaster or for testing purposes, Phoenix DRaaS Failover feature aims to recover virtual machines in the AWS account based on the configuration and failover settings specified in the DR plan.

Types of failover

Phoenix allows you to configure virtual machines for disaster recovery failover in the two modes, Recovery and Test, respectively. You can configure virtual machines for failover with the settings specific to Failover Recovery and Failover Testing. Depending upon the type selected, you can use the corresponding settings to launch the EC2 instance. 

  • Failover Recovery: The Failover Recovery option is used to recover protected virtual machines to AWS in the event of an actual disaster. Failover Recovery ensures that the virtual environment is failed over successfully with a minimal downtime during the disaster. 
    To configure virtual machines for the Failover Recovery mode, you must preconfigure failover settings for the virtual machines. For more information about configuring Failover Recovery settings for virtual machines, see Add failover settings for DR plan.
  • Failover Testing: The Failover Testing option is used to test that the virtual machines are recovered at the recovery site as expected. This operation creates test virtual machines based on the preconfigured virtual machine failover settings specified in the DR plan. Phoenix recommends running Failover Testing in virtual environment periodically to demonstrate the failover setup and identify any possible issues that can occur in the event of an actual disaster. For more information about configuring Failover Test settings for your virtual machines, see Add failover settings for DR plan.

DRaaS failover considerations

Review the following points before triggering a failover of virtual machines.

  • You can launch an AWS instance for a virtual machine associated with the DR plan, only the following exists for the virtual machine:
    • An AMI, if you have deployed the Phoenix AWS Proxy version 4.7.6 or earlier. Or,
    • A DR copy, if you have deployed Phoenix AWS Proxy version 4.8.0 or later. 
  • To configure virtual machines for failover, ensure that you deploy the Phoenix AWS Proxy with version 4.8.0 or later. 
  • For Failover Recovery and Test setups, you should separately configure failover settings. You can configure failover settings at DR plan-level and individual virtual machine-level. Depending upon the type selected for failover, the instance is launched using the corresponding settings.
  • To create a failover request, you must have at least one Phoenix AWS Proxy which is associated with the DR plan and region and registered with Phoenix.  
  • After you initiate failover for virtual machines, you can check the status of the launched EC2 instances on the Jobs tab.
  • AWS allows 20 EC2 instances per region by default. To increase the limit of running instances (more than 20) running at the same time in one region, you must get approval from Amazon. You can increase the instance limit for a specific region. Therefore, you must specify the region where you want to increase your instance limit. To request an increase in your limit, contact Amazon
  • All instances launched in public subnet must have a public IP address and the instances launched in private subnet must not have a public IP address.