Skip to main content

 

Druva Documentation

Manage failover settings

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

To enable failover of the VMware environment in the event of a disaster, you must configure failover settings for virtual machines. This topic provides instructions to perform the following failover tasks:

Add network mappings

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

You can define the target and default network mappings, such as VPC and subnet, for the failed over virtual machines. The target network mapping defines the VPC and subnet to be used during the failover based on the source network present on the virtual machine. The default network mapping defines the VPC and subnet to be used when no target network is specified.

Note: If you have configured a static IP address for a virtual machine, you must validate the IP address with respect to the new VPC and subnet assigned to the failover settings.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
  7. In the Network Mappings section, click Add Mapping.
    Configure_DR_Configure_Network_Mappings.PNG
  8. On the Network Mapping dialog box, provide the following details:
    • 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 your production failover mode. For more information about VPC, see VPC.
      • Subnet: Select the required subnet option from the drop-down list for your production failover mode. For more information, 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, see Subnet.
  9. Click Add.

Edit network mapping

You can edit the target network mapping details, such as VPC and subnet, configured for the failed over virtual machines.

Note: If you have configured a static IP address for a virtual machine, you must validate the IP address with respect to the new VPC and subnet assigned to the failover settings.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
  7. In the Network Mappings section, click the Edit icon.JPG Edit icon.
  8. On the Network Mapping page, edit the required VPC and subnet details.
    Edit_network_mappings.png
  9. Click Save.

Delete network mapping

You can delete the target network mapping configured for the failed over virtual machines. When you delete a mapping, the virtual machines attached to the network mapping will now use the default target mapping configured for failover. Ensure that you verify the IP address settings for the virtual machines attached to the source network and update the details if required.

Note: If you have configured a static IP address for a virtual machine, you must validate the IP address with respect to the new VPC and subnet assigned to the failover settings.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
  7. In the Network Mappings section, click the Delete_icon.JPG Delete icon.
  8. On the confirmation message, click Confirm to delete the network mapping.

Edit default target network

You can edit the default target network details configured for failover of your virtual machines in the production and test environments. The default target network settings are used when no target network is specified.

Note: If you have configured a static IP address for a virtual machine, you must validate the IP address with respect to the new VPC and subnet assigned to the failover settings.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
  7. In the Default production Network section, click the Edit icon.JPG Edit icon to edit the target network settings.
  8. On the Default Target Network dialog box, modify the required VPC or subnet details to be used when no target network is specified.
    Edit_default_target_network_details.JPG
  9. Click Save.

Add failover settings for virtual machines

The VM Failover Settings tab allows you to add failover settings to the virtual machines for disaster recovery.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab in the left pane.
  5. On the DR Plans page, click the DR plan associated with the virtual machine for which you want to configure the failover settings.
  6. On the DR Plan details page, select a virtual machine to add failover settings or select the checkbox next to the VM Name column to select all the virtual machines to add failover settings.
  7. Click the icon and click the VM Failover Settings option from the list.
  8. On the VM Failover Settings page, provide the following failover settings in the Production and Test tabs, respectively.
    DR_VM_FailoverSettings.PNG
    • Instance Type: The type of EC2 instance Phoenix created after the VMware virtual machine is restored in the AWS account using the available DR copy. Select an instance type based on the virtual machine you are configuring for failover. Phoenix does not allow you to select smaller instances, such as t2.nano.
    • IAM Role: Select the required IAM identity role to allow the Phoenix AWS proxy access your AWS account.
    • Volume Type: Select the required type of the Amazon EBS volume that you want to attach to the EC2 instance, such as Magnetic, General Purpose SSD, or Provisioned IOPS SSD. For more information about the volume type options, refer to the AWS documentation

      Note: Select the Provisioned IOPS SSD volume type only if the disk sizes are greater than 4 GB.

      • 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. Keys should not be name or conversion_id as these are used by Druva. For more information about tags, refer to the AWS documentation.
    • Subnet: Displays the segment of the IP address range of a VPC to which you can attach the EC2 instances.

      Note: You cannot edit the subnet details on this page. To edit the subnet details, see Edit network mapping  and Edit default target network sections.

    • Public IP: The public IP address assigned to the virtual machine. The following are the values of the Public IP field:

      Notes

      • You must check the target network mapping used for the source virtual machine. If a VPC endpoint is not configured for the subnet, and,
        • If the subnet associated with the target network mapping is a public subnet, the public IP address should be configured as Auto-Assign or Elastic so that the S3 bucket and the SQS queue are reachable from the failover instance.

        • If the subnet associated with the target network mapping is a private subnet, the public IP address should be configured as None.

      • By default, the public IP will be assigned to None

      • None
      • Elastic
      • Auto-Assign
    • Private IP: The private IP address assigned to the virtual machine. The following are the values of the Private IP field:
      • Auto-Assign
      • Static
        By default, the private IP will be assigned to Auto- Assign.
    • Security Group: Select the required security group from the drop-down list.
  9. Click Save.

Edit failover settings

The VMs tab allows you to edit failover settings for one virtual machine at a time.

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 Manage > Disaster Recovery.
  4. In the DR Plans tab, click the DR plan associated with the virtual machine for which you want to view failover history.
  5. In the VMs tab, select the virtual machine(s) for which you want to modify the failover settings or select the checkbox next to the VM Name column to select all virtual machines.
  6. Click VM Failover Settings.
    The VM Failover Settings page opens with the preconfigured failover settings for that virtual machine.
    VM_FailoverSettings.png
  7. In the Production Failover and Test Failover tabs, select the checkboxes corresponding to the fields to make the fields editable.
  8. From the Instance Type, IAM Role, and Volume Type drop-down lists, select the required failover settings.
  9. In the Instance Tags(Key-Value) boxes, enter the key and value for the tags.
    You can add multiple tags for your EC2 instance.
  10. Click Save.

View failover jobs

The Failover Jobs section on the Recovery tab displays the status of the failover jobs triggered for that DR plan. When you trigger a failover for a virtual machine, a failover request is created and sent to the Phoenix AWS proxy. Phoenix AWS proxy launches the EC2 instance based on the specified failover settings. Phoenix AWS proxy sends the instance status to the Phoenix Cloud.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
    The Failover Jobs section provides the following failover details:
    • Job ID: The unique identification number of the triggered failover job
    • Triggered On: The timestamp and the date details of the triggered failover job.
    • Failover Setup: The disaster recovery failover mode selected for the recovery, such as Production or Test.
    • Status: The status of the failover job.

Cancel a failover job

You can use the Jobs page to manually cancel a DR failover job that is in the running state.

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 Jobs.
  4. On the Jobs page, click the Disaster Recovery tab.
  5. Select the failover job that you want to cancel.
  6. Click Cancel job.
  7. Click Yes on the confirmation message.

The execution of the selected job is canceled.

Edit failover recovery workflow

When you create a DR plan, Phoenix creates a default recovery workflow with a virtual machine boot (VM boot) step containing all virtual machines configured in that DR plan. You can edit this default recovery workflow and add multiple steps to the workflow based on the failover requirements. You can perform the following tasks:

  • Add VM boot steps to the recovery workflow and specify their sequence of execution.
  • Add on-boot scripts for execution after virtual machines boot up.
  • Specify a timeout for the execution of the script.
  • Enable abort settings for a step if you want to cancel a failover job when failover of any virtual machines fails during that step.
  • Add time delays between the execution of the two steps.
  • Move virtual machines from one boot step to another boot step, as required.
  • Change the order of the execution of the steps.
  • Remove a VM boot step from the recovery workflow. To remove a VM boot step, you must first move all virtual machines from that step to another VM boot step.  
  • Remove a time delay step from the recovery workflow.

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 Manage > Disaster Recovery.
  4. In the left pane, click the DR Plans tab.
  5. Click the DR plan associated with the virtual machine for which you want to view the status of the failover jobs.
  6. On the DR Plan details page, click the Recovery tab.
  7. In the Recovery section, click Edit Workflow.
    The Edit Recovery Workflow page displays the default recovery workflow created for the DR plan.
  8. Click Add Recovery Step and select the VM Boot or Time Delay option to add a new step for virtual machines.
    • VM Boot: This option enables you to define a boot sequence for your virtual machines in the DR plan.
      1. In the VM Boot step, click the More icon.PNG icon and click Boot Settings
        VM_Boot_Step.JPG
      2. On the Step XVM Boot dialog box, select the Abort recovery operation if any VM in this boot step fails to boot checkbox to cancel the failover operation on failure of any virtual machine during the execution of this step. Repeat the step to add multiple VM boot steps.
    • Add script: This option enables you to execute a script after the virtual machines boot up.
      1.  Click the More icon.PNG icon corresponding to the virtual machine for which you want to add a script and click Edit Script.
        script_execution.JPG
      2. On the <virtual machine: Script> dialog box, provide the following details:
        • S3 URL: The URL of the script's location in the S3 bucket of your AWS account.
        • Execution Command: The command to be executed.
        • Script Timeout: The script timeout in minutes. You can specify a value between 1 and 1440.
        • Abort failover for this VM if script execution fails: Enable the checkbox to cancel the failover operation on the failure of the script.
      3. Click Save.
    • Time Delay: This option enables you to insert a time delay between the execution of the two steps.
      1. Click Add Recovery Step > Time Delay.
      2. On the Time Delay dialog box, enter the time in minutes in the Time Delay box to delay the execution of the next step in the recovery process. You can specify a value between 1 and 1440.
        Time_Delay_Step.JPG
      3. Click Save.
        You can also edit the time delay that you set while adding a step. You can also delete a step that you need no longer. To edit a time delay or delete a step, click the More icon.PNG icon and click Set Delay or Delete Step.

View failover instances

The Failover Instances tab lists the failover instances launched during failover. 

Procedure

  1. On the Phoenix Management Console menu bar, click All Organizations, and select the required organization from the drop-down list.
  2. On the menu bar,  click Manage Disaster Recovery.
  3. In the left pane, click the Failover Instances tab.
    DR_failover_instances_tab.PNG
  4. The Failover Instances tab displays the following fields:
    • EC2 Instance ID: The unique identification number of the EC2 instance that was launched during failover.
    • VM Name: The virtual machine for which the EC2 instance was launched during failover.
    • Failover Job ID:  The unique identification number of the job triggered during failover. Click the Job ID of the instance to view the details of the failover job.
    • Failover Initiated On:  The date and the timestamp when the failover operation was initiated.
    • Failover Type: The type of failover initiated, such as Production or Test.
    • AWS Account: The account that maintains the DR copy for the virtual machine.
    • Region: The AWS region where you have deployed the Phoenix AWS proxy.
    • Instance Status: The status of the EC2 instance, such as:
      • Pending
      • Running
      • Shutting Down
      • Terminated
      • Stopping
      • Stopped

    Note: For Phoenix AWS  proxy 4.7.6 or earlier, the instance status may show the following value: Pending, Impaired, Insufficient Data, Not Applicable, Initializing, or Stopped/Terminated.

Terminate a failover instance

The Failover Instances tab lists the EC2 instances launched during failover. You can terminate instances that are in the running state.

Note: To terminate the EC2 instances, you must use the Phoenix AWS proxy 4.8.0 or later.

Procedure

  1. On the Phoenix Management Console menu bar, click All Organizations, and select the required organization from the drop-down list.
  2. On the menu bar,  click Manage Disaster Recovery.
  3. In the left pane, click the Failover Instances tab.
  4. On the Failover Instances page, select the checkboxes of the instances that you want to terminate.
    Terminate_instances.JPG
  5. Click Terminate.

Note: After you terminate an instance, the system might take a few minutes to reflect the status of  termination on the Phoenix Management Console.