Phoenix DRaaS workflow
With Phoenix DRaaS, Amazon Machine Image (AMI) copies are created based on the virtual machine backup and maintained in your AWS account. At the time of disaster, you can launch EC2 instance from these AMIs, in-turn spinning up to production in minutes. The AMI copies are updated with the latest virtual machine backup based on the defined schedule. The Phoenix DRaaS workflow is depicted in the following diagram:
Phoenix DRaaS components
When a disaster strikes your VMware environment, the following Phoenix DRaaS components work coherently to fail over your virtual machines, in-turn spinning up to production in minutes.
- Customer datacenter
Consists of a VMware setup registered with Phoenix for backup. The setup comprises a vCenter server or a standalone ESXi server. Virtual machines on the VMware setup are configured for backup by associating them with appropriate backup policies and retention policies. Based on the backup schedules defined in the backup policy, data is backed up regularly to the Phoenix Cloud in AWS.
- Customer AWS account
Your account in AWS that acts as a secondary site for Phoenix DRaaS.
- Phoenix AWS proxy
An EC2 instance in your AWS account that runs a Phoenix service. The Phoenix AWS proxy replicates data from the Phoenix storage to your AWS account and creates an AMI copy at a frequency specified in the disaster recovery (DR) plan.
- Disaster recovery plan
The DR pan encompasses virtual machines configured for disaster recovery, the AWS account used for disaster recovery, the AMI update frequency, and the network, security, and instance-related failover settings, such as VPC, subnet, security group, IP addresses, 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 AMI and failover settings, an EC2 instance is launched in your AWS account. For more information about Phoenix Disaster Recovery Failover, see Disaster Recovery Failover.