Phoenix DRaaS feature leverages the existing AWS cloud offerings for faster recovery of your VMware environment by eliminating the infrastructure burden and significantly reducing downtime. It ensures business continuity of your VMware environment by facilitating the recovery of your virtual machines on demand in the cloud in the event of a disaster. You must therefore configure your VMware environment for disaster recovery.
Configure the virtual machines for disaster recovery using the following steps:
- Step 1: Set up Phoenix AWS proxy
- Step 2: Create a DR plan
- Step3: Add virtual machines to the DR plan
- Step 4: Configure the failover settings for DR plan
Note: You cannot associate one virtual machine to multiple DR plans.
Create Disaster Recovery plan
A DR plan lets you select virtual machines from multiple registered vCenters/ESXi hosts and server groups, and provides settings required during failover for disaster recovery.
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.
- Phoenix AWS proxy is deployed in the same AWS region where the virtual machines you want to configure for disaster recovery are being backed up.
- Phoenix AWS proxy is upgraded to the latest available version.
- Log on to Phoenix Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Manage > Disaster Recovery.
The Manage Disaster Recovery page opens with the DR plan tab opened, by default. The DR plans tab lists the available DR plans.
- Click Create New DR plan.
The Add DR plan page opens.
- Provide the following information to create a DR plan.
|plan Name||The name for the DR plan that you want to create.|
|Description||The description for the DR plan.|
AMI Update Frequency
The frequency to update an AMI. Based on the frequency defined, data is replicated from Phoenix storage to your AWS account and an AMI is created that corresponds to the latest restore point available for the virtual machine. If there is already an existing AMI present for a virtual machine (based on the previous restore point), it is replaced by the AMI created for the latest available restore point.
Select one of the following options from the drop-down list:
|Start Time||The time when you want the AMI update operation to begin.The Start Time list appears only if you select the Daily or Weekly options from the AMI Update Frequency drop-down list.|
The account that will be used to maintain the AMI for the virtual machine. At the time of disaster, you can launch EC2 instance from this AMI, in-turn spinning up to production in minutes.
Select the required account from the drop-down list.
The storage region where you want to create AMIs for your virtual machines.
Select the required region from the drop-down list.
- Click Next.
The DR plan gets created. You can add virtual machines to your DR plan.
Add virtual machines to Disaster Recovery plan
Phoenix allows you to add virtual machines from multiple registered vCenters/ESXi hosts and server groups to the DR plan. In order to recover your virtual machines in the event of a disaster, you must add virtual machines to the DR plan. Phoenix creates AMI copies periodically based on the schedule defined in the plan and maintains the copies in your AWS account. At the time of disaster, you can launch EC2 instances from these AMIs, in-turn spinning up to production in minutes. The AMI copies are updated with the latest virtual machines 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 same as the region specified in the DR plan.
- Once a virtual machine is added to a DR plan, AMI for that virtual machine will be created periodically as per the schedule specified in the DR plan.
- When adding a virtual machine to a DR plan, the virtual machine-specific failover settings for launching instance with its AMI are set 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
- On the Add DR plan page, under the Select VMs tab, select the virtual machines listed under the Virtual Machine column that you want to add to the DR plan.
Note: You can add multiple virtual machines to a DR plan. However, before adding virtual machines to a DR plan, you must ensure that the count of the current DR licenses used is not more than the count of the purchased licenses. For more information about DR Licenses, see DR licensing.
- Click Next.
After you add virtual machines to the DR plan, Phoenix creates AMI copies based on the DR plan schedules and stores the AMI information in the DR plan.
Add failover settings for DR plan
This topic provides instructions to configure the virtual machines settings for Disaster Recovery Failover. In order to failover your VMware environment in the event of 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, Failover Recovery and Failover Test, respectively, for individual virtual machines in the DR plan. For more information, see Manage failover.
- On the Add DR plan page, under the Failover Settings tab, provide the following details in the Failover Recovery and Failover Test columns.
The section of the AWS Cloud that is dedicated to your AWS account. You can launch the AWS resources, such as EC2 instances, in your virtual network.
Select the VPC option from the drop-down list where you want to launch the EC2 instance.
The segment of the IP address range of a VPC to which you can attach the EC2 instances. A subnet groups the instances according to the security and operational needs.
Select the required subnet option from the drop-down list.
A set of inbound and outbound network connections for the EC2 instance. A security group comprises a list of protocols, ports, and IP address ranges.
Select the required security group from the drop-down list.
Note: You can configure IP settings on the DR plan details page.
- Click Save.