Skip to main content

 

Druva Documentation

Manage Failover

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

To enable failover of your VMware environment in the event of a disaster, you must configure failover settings for your virtual machines. This article provides instructions to manage failover settings specific to the virtual machine in the DR plan. It also describes how to view statuses of the failover requests for virtual machines. 

You can also configure failover settings at the level of the DR plan. For more information, see Add failover settings.

Add failover settings for virtual machine

The VMs tab allows you to add failover settings for virtual machines.

Procedure

  1. Log on to 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
    The Manage Disaster Recovery page opens with a list of available DR plans.
  4. Click the DR plan associated with your virtual machine for which you want to trigger failover.
    The DR Plan details page opens.
  5. Click the DR plan associated with your virtual machine for which you want to configure the failover settings.
  6. Click the VMs tab.
    The VMs tab lists all the virtual machines associated with the DR plan that you have selected.
  7. Click the required virtual machine and click VM Failover Settings.
  8. The Update DR Plan page opens. Provide the following details:

Field

Description

Instance Type

A copy of the Amazon Machine Image (AMI) that runs as a virtual server in the AWS Cloud.

Public IP

The IP addresses that are reachable from the Internet. You can use public IP addresses for communication between your instances and the Internet.

Select one of the following options:

  • None: Use this option when you want to assign the only private IP address to the instance so that the machine is inaccessible over the Internet.

Note: When you set the public IP address of your instance as 'None', you should have another instance assigned with a public IP address. This allows you to access private IP address assigned to your instance using the public IP address.

  • Elastic: Use this option when your instance does not have a public IP address, and you want to associate a static elastic IP address to your instance to enable communication with the Internet. It allows you to mask the failure of an instance by rapidly remapping the address to another instance in your account.
  • Auto-Assign: Use this option to assign the IP address to the instance automatically from the EC2-Classic public IP address pool.

Private IP

The IP addresses that are not reachable from the Internet. You can use private IP addresses for communication between instances in the same network, such as VPC.

Select one of the following options:

  • Static: Use this option to assign an IP address to the instance from your pool of IP addresses. 
  • Elastic: Use this option to remap your IP addresses from one instance to another, within the network of the instance.
  • Auto-Assign: Use this option to assign the IP address to the instance automatically from the EC2-Classic public IP address pool.

Note: You must use private IP addresses from the CIDR range of the subnet of the instance. Amazon does not allow you to use the first four IP addresses and the last IP address from the CIDR range. Therefore, we strongly recommend you to avoid using these IP addresses.

  1.  Click Save.

Edit failover settings

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

Procedure 

  1. On the VMs tab, click the virtual machine for which you want to modify the failover settings.
  2. Click VM Failover Settings.
    The Update DR Plan page opens with the preconfigured failover settings for that virtual machine.
  3. Edit the options in the Instance Type, Public IP, and Private IP drop-down lists under the Failover Recovery and Failover Test columns.
  4. Click Save.

View recent failovers

You can view failovers occurred lately for virtual machines associated with a DR plan. Phoenix DRaaS keeps a record of the failovers occurred recently for the virtual machines and the type of failover triggered for these virtual machines. 

Procedure

  1. Log on to 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
    The Manage Disaster Recovery page opens with a list of available DR plans.
  4. Click the DR plan associated with your virtual machine for which you want to view failover history.
    The DR Plan details page opens. 
  5. Under the Summary tab, the Recent Failovers section displays a list of failover types for that DR plan along with the failover date and timestamp.
    Recent failover.PNG

 View failover history

The Failover History tab displays the status information for each virtual machine failover. When you trigger failover for a virtual machine, a failover request is created and sent to the Phoenix AWS proxy. Phoenix AWS proxy uses AWS APIs to launch the instance with the specified parameters. Phoenix AWS proxy sends the instance status to the Phoenix Server.

Procedure

  1. Log on to 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
    The Manage Disaster Recovery page opens with a list of available DR plans.
  4. Click the DR plan associated with your virtual machine for which you want to view failover history.
    The DR Plan details page opens.
  5. Click the Failover History tab. The tab displays the following failover details.

     

Field

Description

Virtual Machine

The name of the virtual machine for which the failover was requested.

vCenter/Hypervisor

The vCenter Server or the ESXi that hosts your virtual machine.

Server Group

The server group associated with the virtual machine.

Failover Initiated on

The date and timestamp when the failover was triggered.

AMI Name

The AMI copy used during the failover to launch EC2 instance.

EC2 Instance ID

The unique identification number of the EC2 instance that was launched during failover.

Failover Status

The status of the launched EC2 instance. The following are the possible statuses of the EC2 instance:

  • Requested: A request to launch an EC2 instance is triggered.
  • Initializing EC2 instance: A request is sent and an instance launch is initialized.
  • Complete: The launch of the EC2 instance is completed.
  • Request failed: The launch of the EC2 instance has failed. 

Public IP

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

  • None
  • Elastic
  • Auto-Assign

By default, the public IP will be assigned to ‘None’. For more information about the public IP options, see Public IP options.

Private IP

The private IP address assigned to the virtual machine. The following are the possible values of the Private IP field:

  • None
  • Auto-Assign
  • Static

By default, the private IP will be assigned to ‘Auto- Assign’. For more information about the private IP options, see Private IP options.

  1. On the top-right corner of the screen, select the options in the vCenter/Hypervisor and Server Group filters to list virtual machines based on the vCenter Server or Hypervisor host, and Server Groups that the virtual machines are associated with.
  2. Click Clear to reset the filters.