Skip to main content
Druva Documentation

Create a disaster recovery plan

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

 We strongly discourage the use of Phoenix CloudCache with Phoenix DRaaS as the CloudCache can impact the RPO especially if the DR job is configured to run immediately after backup. The data is pulled from the Phoenix CloudCache (in case the data is not synced to the Phoenix Cloud yet) and restored to the customer AWS account, which can impact the performance of the DR restore job. There is no impact if the DR job is configured to run daily or weekly, and the data is already present on the Phoenix Cloud.

What is a disaster recovery plan

A Disaster Recovery (DR) plan defines the following:

  • AWS account: The account in AWS that acts as a secondary site for Phoenix DRaaS. The account maintains the DR copies for the virtual machines. At the time of disaster, you can launch EC2 instances from these DR copies, in-turn spinning up to production in minutes.
  • AWS region: The storage region where you want to create DR copies for the virtual machines. The region of the DR plan and region of the storage to which the virtual machine is backing the data to must be same.
  • Replication frequency: The frequency at which Phoenix updates the DR copy. Based on the defined frequency, on each schedule, the existing DR copy, if present, is replaced with a DR copy based on the latest restore point available for the virtual machine.

Note: If you have deployed the Phoenix AWS proxy with version 4.7.6 or earlier, the replication frequency defines the frequency at which Phoenix updates the AMI. Based on the defined frequency, on each schedule, the existing AMI, if present, is replaced with an AMI based on the latest restore point available for the virtual machine.

In other words, the DR plan encompasses the virtual machines configured for disaster recovery, the AWS account used for disaster recovery, the replication frequency, and the network, security and instance-related failover settings such as VPC, subnet, IP addresses, security group, and instance type. Preconfiguration of these settings in the DR plan allows for a single-click failover in the event of a disaster. On failover, based on the latest DR copy and failover settings, an EC2 instance is launched in the AWS account. You can failback the failed over EC2 instance to recover the virtual machine back in your vCenter environment.

Phoenix DRaaS feature leverages the existing AWS cloud offerings for faster recovery of the VMware environment by eliminating the infrastructure burden and significantly reducing downtime. It ensures business continuity of the VMware environment by facilitating the recovery of virtual machines on demand in the cloud in the event of a disaster. You must, therefore, configure the VMware environment for disaster recovery.

Watch the following video to know more about creating disaster recovery plan.

 

How do I create a disaster recovery plan

Configure the virtual machines for disaster recovery using the following steps:

Configure_DR_workflow.png

Step 1: Set up Phoenix AWS proxy

For more information about how to set up Phoenix AWS proxy, see Phoenix AWS proxy setup workflow. 

Step 2: Create a disaster recovery plan

You can configure virtual machines for disaster recovery by adding them to a DR plan. A DR plan lets you select virtual machines from the multiple registered vCenters/ESXi hosts and administrative groups. The DR plan contains necessary settings, such as the replication frequency, the AWS account where the DR copies are stored, and failover settings used for the production and test failovers.

Considerations for creating a DR plan

Before creating a DR plan, you must consider the following points:

  • You have at least one Phoenix AWS proxy deployed in your AWS account that you intend to use for disaster recovery.
  • You deploy Phoenix AWS proxy in the same AWS region where the virtual machines you want to configure for disaster recovery are being backed up.

Procedure

  1. Log in to the Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Disaster Recovery.
  4. In the left pane, click the DR Plans tab. The DR Plans page lists the DR plans configured with your organization.
  5. On the top-right corner of the page, click Create New DR Plan.
    The Create DR Plan page opens.
  6. In the Plan Details tab, provide the following details to create a DR plan.
    DR_Configure_DR_Plan_Details.jpg
  • Plan Name: The name of the DR plan that you want to create.
  • Description: The description of the DR plan.
  • AWS Account: The account that will be used to maintain the DR copy of the virtual machine. At the time of the disaster, you can launch EC2 instance from this DR copy, in-turn spinning up to production in minutes. Select the required account from the drop-down list.
  • Region: The storage region where you want to create DR copies for your virtual machines. Select the required region from the drop-down list.
  • Replication Frequency: The frequency to update a DR copy. Based on the frequency defined, the Phoenix AWS proxy replicates the virtual machine backup data from the Phoenix Cloud to the AWS account and creates a DR copy. The DR copy corresponds to the latest restore point available for the virtual machine. If there is already an existing DR copy present for a virtual machine (based on the previous restore point), it is replaced by the DR copy created for the latest available restore point. 
    Select one of the following options from the drop-down list
    • Immediately after backup: The update DR copy job (DR Restore job on the jobs page) starts immediately after a successful virtual machine backup.
    • Daily: The update DR copy job starts every day at the selected time.
    • Weekly: The update DR copy job starts every week at the selected time.
  • Start Time: The time when you want the update DR copy job to begin. The Start Time list only appears if you select the Daily or Weekly options from the Replication Frequency drop-down list.
  1. Click Next to add virtual machines to your DR plan.

You must now add virtual machines to your DR plan 

Step 3: Add virtual machines to the disaster recovery plan

Phoenix allows you to add virtual machines from multiple registered vCenters/ESXi hosts and administrative groups to the DR plan. In order to recover virtual machines in the event of a disaster, you must add virtual machines to the DR plan. Phoenix creates DR copies periodically based on the schedule defined in the plan and maintains the copies in the AWS account. At the time of the disaster, you can launch EC2 instances from these DR copies, in-turn spinning up to production in minutes. The DR copies are updated with the latest virtual machine's backup based on the defined schedule. 

Considerations for adding virtual machines to the DR plan

Before adding a virtual machine to a DR plan, you must consider the following points:

  • You can add only those virtual machines to a DR plan for which the storage region for backup is the same as the region specified in the DR plan.
  • You cannot add the same virtual machine to multiple DR plans.
  • Once you add a virtual machine to a DR plan, DR copies for that virtual machine is created periodically as per the schedule specified in the DR plan.
  • When adding a virtual machine to a DR plan, Phoenix sets the virtual machine-specific failover settings for launching an instance with its DR copy to the predefined default values. You can edit these settings later. The following are the default settings specific to virtual machines:
    • instance_type = t2.micro
    • public_ip = None
    • private_ip = Auto Assign

Procedure

  1. On the Create DR Plan page, click the VM Selection tab.
    The Source VMs section lists the virtual machines.
  2. Select the virtual machines listed under the VM Name column that you want to add to the DR plan or select the checkbox next to the VM Name column to add all the virtual machines to the DR plan.
    DR_Configure_VM_Selection.jpg
  3. In the search box, you can enter the name of the virtual machine, hypervisor, or an administrative group to list the associated virtual machines. 

    Note: You can add a virtual machine only to a single DR plan. Therefore, the VM  Name column does not list virtual machine s that are already added to another DR plans.

  4. Click Next.

After you add virtual machines to the DR plan, Phoenix AWS proxy creates DR copies based on the DR plan schedules and stores the DR copy information in the DR plan.

Step 4: Add failover settings to the disaster recovery plan

This section provides instructions to configure the settings of the virtual machine for failover. To failover VMware environment in the event of a disaster, you must configure failover settings for your virtual machines. Phoenix allows you to configure failover settings specific to the DR plan as well as individual virtual machines in the DR plan. When you configure failover settings for a DR plan, the failover settings apply to all the virtual machines associated with the plan.

Note: You can configure two sets of the failover settings, Production Failover settings and Test Failover settings, respectively, for individual virtual machines in the DR plan. For more information, see Manage failover.

Procedure

  1. On the Create DR Plan page, click the Failover Settings tab.
  2. In the Production Failover Settings section, provide the following failover settings:
    DR_Configure_Failover_Settings.jpg
  • Instance Type: Select the instance type appropriate for your AWS resource.
  • IAM Role: Select the required IAM identity role to attach to the Phoenix AWS proxy.
  • Volume Type: Select the required type of the Amazon EBS volume that you want to attach to the EC2 instance.Select one of the following options:
    • Magnetic: These are standard volumes backed by the magnetic drives and used for workloads that are infrequently accessed. These volumes deliver approximately 100 IOPS on average. For more information, refer to the AWS documentation.
    • General Purpose SSD: These are cost-effective storages that are used for a broad range of workloads. These volumes deliver approximately between 100 to 16,000 IOPS on average. For more information, refer to the AWS documentation.
    • Provisioned IOPS SSD: These provisioned storages are used for I/O-intensive workloads such as database workloads. These volumes deliver approximately between 100 to 64,000 IOPS on average. For more information, refer to the AWS documentation.
      • IOPS: Enter the input/output operations per second capacity for the volume.  The IOPS box is displayed only if the Provisioned IOPS SSD option is selected as the volume type.
  • Instance Tags (Key-Value): Enter a label in the key-value format and assign it to your AWS EC2 resources to categorize the AWS resources in different ways. For more information about tags, refer to the AWS documentation.
  1. Click Add to add the target network mapping details.
  2. In the Test Failover Settings section, provide failover settings for the test configuration or select the Same as production settings checkbox to use the production settings for the test configuration.
  3. Click Next to define the network mappings.

Step 5: Define network mapping

Note: Ensure that you have deployed Phoenix backup proxy 4.8.2 or later.

The Network Mapping tab enables you to map the VCenter source network to a VPC and subnet on the target AWS account. If the network of your virtual machine belongs to the same network for which you have defined the network mapping, the same VPC and subnet defined in the network mappings are used during failover. The default network mapping defines the VPC and subnet to be used when no target network mapping is specified for the virtual machine source network.

When the source virtual machine has multiple network adapters, the default network mapping settings are always used for failover. However, when the source virtual machine has a single network adapter and if network mappings are defined for the adapter network, these network mapping settings are used for failover. Else the default network mapping settings are used for failover.

Considerations for adding network mappings

Before defining network mappings, you must consider the following points:

  • If a vCenter source network name is renamed, Phoenix DRaaS treats this network as a new network. The corresponding network mapping with the old name is displayed on the Recovery tab with the following warning message:
    Source network does not exist.
  • If a data center name changes, all the source networks within that data center are considered as new networks.
  • For every vCenter, a cron job runs every 24 hours to detect any network changes in your infrastructure. If Phoenix DRaaS detects any change in the source network of a virtual machine, it checks for any available network mapping for the new network. If it does not identify any network mapping, it assigns the default network mapping to the failover settings of the virtual machine. Phoenix DRaaS sends the following alert:
    Failover IP address settings for <virtual_machine_name> is changed.
    If you have configured a static IP address for this virtual machine, you must validate the IP address with respect to the new VPC and subnet assigned to the failover settings.

Procedure 

  1. In the Target Network Mapping section, click Add Network Mapping.
    Configure_DR_Configure_Network_Mappings.PNG
  2. On the Network Mapping dialog box, perform the following:
    • vCenter/Hypervisor: Select the registered vCenter or hypervisor host for which you want to define the VPC and subnet.
    • Source Network: Select the network of your source virtual machine.
    • Production Failover Mapping section:
      • VPC: Select the VPC option from the drop-down list where you want to launch the EC2 instance. For more information about VPC, see VPC.
      • Subnet: Select the required subnet option from the drop-down list. For more information about Subnet, see Subnet.
    • Test Failover Mapping section:
      • VPC: Select the VPC option from the drop-down list where you want to launch the EC2 instance for your test failover mode. For more information about VPC, see VPC.
      • Subnet: Select the required subnet option from the drop-down list for your test failover mode. For more information about Subnet, see Subnet.
  3. Click Add.
    The network mapping for your production and test failover environment gets listed in the Target Network Mapping section. Click Add Network Mapping to add more source mappings for failover.
  4. In the Default Target Network section, specify the VPC and subnet details to be used when no target network is specified.
  5. Click Finish.

The new DR plan is listed on the DR Plans page.

  • Was this article helpful?