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 your virtual machines in your AWS account based on the configuration and failover settings specified in the DR plan.

Types of Failover

Phoenix allows you to configure your virtual machines for DRaaS Failover in 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 your virtual environment be failed over successfully with a minimal downtime during disaster. 
    To configure virtual machines for the Failover Recovery mode, you must preconfigure failover settings for your virtual machines. For more information about configuring Failover Recovery settings for your 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 you to run Failover Testing on your virtual environment periodically to demonstrate your 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 failover of your virtual machines.

  • You can launch an AWS instance for a virtual machine that is associated with the DR plan, only if an AMI exists for that virtual machine.
  • To configure virtual machines for failover, ensure that the Phoenix AWS Proxies are upgraded to version 4.6.3 or later. Else, failover cannot be initiated for the DR plan associated with the virtual machines.
  • For Failover Recovery and Test setups, you should separately configure failover settings. You can configure failover settings at DR plan-level and at individual virtual machine-level. Depending upon the type selected for failover, instance is launched using the corresponding settings.
  • To create failover request, at least one Phoenix AWS proxy associated with the DR plan should be connected to the Phoenix Server.
  • After you initiate failover for virtual machines, you can check the status of the launched EC2 instances in the Failover History tab.
  • When you create an EC2 account with Amazon, by default, your account is limited to a maximum of 20 running instances per EC2 region. To increase the limit of running instances (more than 20) running at the same time in one EC2 region, you must get an approval from Amazon. The instance limit can be increased for a specific region. Therefore, you must specify the EC2 region where you want to increase your instance limit. To request for an increase in your limit, contact Amazon