Skip to main content
Documentation

 

Druva Documentation

Manage virtual machines

  1. Last updated
  2. Save as PDF

​

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

​

Overview

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. 

To view virtual machines configured for disaster recovery

  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. Click Disaster Recovery. 
    The Disaster Recovery page opens.

  4. Select a DR plan from the Select DR plan dropdown list.  

  5. In the left navigation bar, click Virtual Machines. 

Virtual machine details

The following details of the VMs that are configured are disaster recovery is available. 

Field  Description
VM Name Name of the virtual machine.
Last backup status When was the last backup run and its status. 
DR Enabled Indicates if disaster recovery is enabled for the VM. 
Prerequisite Check Status of the prerequisite checks. See, DRaaS failover prerequisite checks. 
Last DR Restore Status When was the last DR restore job completed and it's status. 
RPA Recovery Actual Point (RPA) represents the time elapsed since the last successful snapshot of the VM that is available for failover. See, Managing Recovery Point Actual (RPA).
Failover settings Hover to view the details of the test and production failover settings. 

Operations for virtual machine management

You can perform the following operations to manage your virtual machines for disaster recovery. 

Operation Description
VM Failover settings

You can update the production and test failover settings. 

See, Manage disaster recovery failover. 
Add VM

You can add virtual machines from multiple registered vCenters/ESXi hosts and administrative groups to an exisitng DR plan. You can also configure the failover settings while you add the VMs to the DR plan.

You can add only those VMs that are configured for backup by Druva. 

See, Add virtual machines to and existing DR plan.
Update DR copy Phoenix regularly updates the DR copy of the backed up virtual machines based on the schedule defined in the DR plan set during configuration. In addition to the scheduled DR copy update, you can manually update the DR copy at any time.
Enable DR You can enable disaster recovery for a virtual machine associated with a DR plan to recover the backup data in the event of a disaster. After enabling, the DR copies are updated for the virtual machines and you can failover virtual machines using these DR copies.
Disable DR You can disable the disaster recovery service for a virtual machine associated with a DR plan at any time. After disabling, the DR copies not updated for the virtual machines. However, you can failover the virtual machine using the last DR copy created before the DR was disabled. The DR copy updates will resume only after you enable the service on the virtual machine.
Remove VM You can unconfigure virtual machines from the configured DR plan. When you unconfigure virtual machines from a DR plan, the assets created during the previous DR copies get deleted. Failure of deletion of assets generates an alert containing assets details.

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

To add virtual machines to an existing DR plan

  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. Click Disaster Recovery. 
    The Disaster Recovery page opens.

  4. Click the DR plan to which you want to add virtual machines. Alternatively, you can select a DR plan from the Select DR plan dropdown list.  

  5. In the left navigation bar, click Virtual Machines, and click Add VMs. 

  6. The Add VMs page opens with a list of the configured virtual machines and details, such as the registered vCenter/ESXi hosts and administrative groups.

    Note: The Add VMs page displays only those virtual machines which are configured for backup.

  7. Select the virtual machines that you want to add to the DR plan.
  8. Click Next and update the failover settings for the virtual machines you want to add. 

To add failover settings for the newly added VMs

  1. From the Recovery Step dropdown list, select the recovery step for the VM to be included in the recovery workflow.
  2. Update the Production Failover settings.

    Add_VMs.png

    Provide the following failover settings for production and test failover, respectively. You can choose to retain the production failover settings for test failover. 

    Configure the following options for failover:

    Option Description
    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.

    See,  Failover Limitations.
    IAM Role

    With the implementation of AWS PrivateLink (If you have deployed a Phoenix AWS proxy version 4.9.1-101573 or later), only the existing IAM roles will be displayed in the IAM Role drop-down. If you have created a new IAM role in your AWS account, you need to manually type the name of the IAM role which is the IAM instance profile ARL name.

    For more information, refer to the AWS documentation.
    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.

    Note: Select the Provisioned IOPS SSD volume type only if the disk sizes are greater than 4 GB
    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.

     

  1. Click Finish.