Skip to main content
Druva Documentation

Phoenix disaster recovery workflow and components

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

Phoenix DRaaS components

When a disaster strikes the VMware environment, the following Phoenix DRaaS components work coherently to failover virtual machines, in-turn spinning up to production in minutes.

► Customer datacenter
A customer datacenter consists of a VMware setup registered with Phoenix for backup. The setup comprises of vCenter hosts or standalone ESXi hosts. You can configure virtual machines on the VMware setup for backup by deploying a Phoenix backup proxy for VMware, and specifying backup policies and retention policies for the backed up virtual machines. Based on the backup schedules defined in the backup policy, the Phoenix backup proxy regularly backs up virtual machines and stores the virtual machine backup snapshots in the Phoenix Cloud.
► Customer AWS account
The customer AWS account is an account in AWS that acts as a secondary site for Phoenix DRaaS.
► Phoenix AWS proxy
A Phoenix AWS proxy is an EC2 instance in your AWS account that runs the Phoenix Disaster Recovery service. The Phoenix AWS proxy replicates the latest virtual machine snapshots from the Phoenix Cloud to the DR copy in the AWS account at a frequency specified in the disaster recovery (DR) plan.
► Disaster recovery plan
The DR plan encompasses virtual machines configured for disaster recovery, the AWS account used for disaster recovery, the replication frequency, and the network, security, and instance-related failover settings, such as VPC, subnet, security group, IP addresses, and instance type. Preconfigure these settings in the DR plan for a single-click failover in the event of a disaster. On failover, based on the latest DR copy and failover settings, an EC2 instance is launched in your AWS account. For more information about Phoenix Disaster Recovery Failover, see Disaster Recovery Failover.

Phoenix DRaaS workflow for Phoenix AWS proxy 4.8.0 and later

With Phoenix DRaaS, the Phoenix AWS proxy:

  • Reads the virtual machine backup data from the Phoenix Cloud
  • Replicates the virtual machine to an EBS volume
  • Creates an EBS snapshot of the EBS volume called a DR copy in your AWS account
  • Deletes the EBS volume

The Phoenix AWS proxy replicates the entire virtual machine the first time it creates a DR copy. Subsequently, it incrementally updates the DR copy based on the replication frequency specified in the DR plan. This DR copy replaces the copy that is present in your AWS account.  Phoenix AWS proxy maintains only the latest DR copy of a virtual machine. At the time of failover, the Phoenix AWS proxy:

  • Converts the available DR copy to an EBS volume
  • Injects drivers into this EBS volume that is required to boot up the EC2 instance
  • Starts the EC2 instance, in turn spinning up to production in minutes

You can failback the EC2 instances (failed over) and recover the virtual machine with a single click in your virtualization infrastructure in a few hours after it has been recovered to your AWS account during failover.

The following diagram depicts the Phoenix DRaaS workflow:

DR Failback Workflow.png

Note: The Phoenix AWS proxy versions 4.8.0 and later no longer use the AMIs of the virtual machines stored in your account that were created using Phoenix AWS proxy version 4.7.6 or earlier.  When you deploy a new Phoenix AWS proxy with version 4.8.0 or later in your AWS account, the backup data is maintained as DR copies instead of AMI copies in the AWS account. You cannot automatically upgrade the Phoenix AWS proxy from version 4.7.6 or earlier to version 4.8.0 or later. To upgrade the Phoenix AWS proxy, deploy its latest version of in your AWS account. For more information, see Launch Phoenix AWS proxy and Register Phoenix AWS proxy. For more information about the latest version of the Phoenix AWS proxy, see the Druva downloads page

Phoenix DRaaS workflow for Phoenix AWS proxy version 4.7.6 or earlier

With Phoenix DRaaS, Amazon Machine Image (AMI) copies are created based on the virtual machine backup and maintained in the AWS account. At the time of disaster, you can launch EC2 instance from the AMIs, in-turn spinning up to production in minutes. Phoenix updates AMI copies with the latest virtual machine backup as per the defined schedule. The following diagram depicts the Phoenix DRaaS workflow:

Disaster Recovery workflow.png

Related articles