Skip to main content
Druva Documentation


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


►What does Druva offer for business continuity?

Druva Phoenix offers cloud-based, enterprise-scale backup and disaster recovery solutions for business continuity.

►How is disaster recovery different from a regular backup?

In the event of disaster recovery, you can recover data to a failover site in a few minutes, offering tighter RTOs by using ready-to-go images of the production servers as compared to backup solutions where the RTOs are comparatively higher when restoring data back to the production environment.

►How do I deploy Phoenix DRaaS?

After you buy a license, you must deploy Phoenix AWS Proxy. For more information, see Set up Phoenix AWS proxy.

►What is the expected RTO of Phoenix DRaaS?

The expected RTO is in minutes. It is same as the time it would take to launch an EC2 instance from an AMI.

►What is the expected RPO of Phoenix DRaaS?

The expected RPO largely depends on the backup frequency, and the time it takes to complete a DR job. In case you have scheduled to run an AMI update immediately after the backup job, the RPO for DR would be the maximum value of the backup frequency and the time to complete the DR job. For an average-sized virtual machine (500 GB) with 2% change rate, it takes about 3 hours to complete the DR job.

►What are the VMware versions supported for disaster recovery?

For more information about the supported VMware vCenter Server and ESXi, see the Support matrix.

►Which server operating systems does Druva support for disaster recovery?

Druva currently supports only the VMware environment for disaster recovery. For more information about the supported operating systems, see DRaaS support matrix.

►Does Phoenix DRaaS support physical machines?

No. Phoenix DRaaS currently does not support physical machines.

►What is Phoenix DRaaS Pricing?

Elite edition customers get Phoenix DRaaS pre-packaged. Whereas, Enterprise edition customers need to purchase this feature for an additional cost. This feature is not available for Business edition customers.

►Is there any additional cost incurred apart from the cost for using Phoenix DRaaS capabilities?

You would incur a cost for running the Phoenix AWS Proxy, Phoenix storage (that stores the raw data from which AMI copies are created), and AMI copy, which is used to launch an EC2 instance for failover. If you perform failover, you will incur additional cost for the launched EC2 instance.

►What is the Phoenix DRaaS Failover process?

Phoenix DRaaS creates AMI for virtual machines and maintains AMI in the AWS account. At the time of disaster, you can launch EC2 instance from the latest AMI, in-turn spinning up to production in minutes.

►Can I failover a virtual machine to any Restore Point?

No. By default, the latest AMI available (based on the last successful DR job) will be used to launch an EC2 instance for failover. You cannot choose any particular Restore Point for failover.

►Does Phoenix overwrite an AMI on every DR cycle?

No. Phoenix does not overwrite an AMI. Phoenix creates a new AMI with every DR job, and deletes the previous AMI after the creation of the new AMI.

►Can I access an AMI after an instance is launched for disaster recovery?
Yes. If an instance is launched from an AMI for disaster recovery, we do not delete the AMI.

►How do I locate the AMI created in my AWS account?

You can search for the AMI ID based on the AWS region. For more information about retrieving AMI ID, see Get AMI ID.

►How do I search for the EC2 instances created post failover?

The Failover History tab of the DR Plan details page provides the status of the failover requests for virtual machines. You can look for the EC2 instance ID and IP address corresponding to the virtual machine. For more information about viewing failover history, see View failover history.

►Can I configure a virtual machine to replicate data in any AWS region?

No. By default, Phoenix replicates data and creates AMI in the same region where you back up the virtual machines. Phoenix DRaaS requires you to deploy at least one AWS Proxy in the AWS account in the same region (the region where you are backing data) before you can configure the virtual machine for disaster recovery for that account.

►Can I configure a virtual machine to allow a failover to any AWS region?

No. As a part of the failover settings, you can select only those VPCs in the AWS account that belong to the same region as the backup storage.

►Can I configure the same virtual machine to replicate data and perform failover to multiple AWS accounts?

No. You can configure virtual machines to replicate data and perform failover to only one AWS account.

►Is the data secured when transferred from Phoenix storage to customer AWS account?

The Phoenix DRaaS solution is built on top of Phoenix's "already established" secure backup solution (the backup data stored in Phoenix Cloud is encrypted using digital envelope encryption). This data is securely transferred in its encrypted form to the customer’s AWS account. In the customer’s account, the data is decrypted to create an AMI.

►How much data is transferred from Phoenix storage to customer’s AWS account with each DR job?

When the DR job runs for the first time, the entire raw data corresponding to the latest backup stored in Phoenix storage is transferred to the customer’s AWS account. For subsequent DR jobs, only incremental data since the last DR job, is transferred to the AWS account.

►What does Phoenix need for the DRaaS service?

Phoenix needs the following for the DRaaS service:

  • Customer AWS account.
  • DR Proxy deployed and activated to perform the data decryption and DR copy creation. The DR Proxy creates a Phoenix storage bucket to store data, which is used to create AMI.
  • Permissions in the form of an IAM Role and IAM Policy for the DR Proxy to perform Phoenix storage copy and AMI creation.

►What does CloudCache provide for Phoenix DRaaS apart from the data caching capabilities?

We strongly discourage the use of CloudCache with Cloud DRaaS as CloudCache can impact the RPO.

►In addition to the Phoenix DRaaS, what reporting or auditing capabilities Phoenix provide?

Phoenix provides the following capabilities:

  • Lists all the active and completed DR jobs on the Jobs page.
  • Provides alerts for DR job failures.
  • Generates the Disaster Recovery Activity report.
  • Provides the failover history to share the status details of failover requests for virtual machines.

►Can I register multiple organizations in Phoenix to a single AWS account?

Yes. You can register same AWS account to multiple Phoenix organizations. However, you have to set up the Phoenix AWS proxy for each organization. For more information, see Quick steps to set up Phoenix AWS proxy.

►Where will the virtual machines be replicated if I choose the same AWS account when I set up disaster recovery across organizations?

When you launch the Phoenix AWS proxy, on the AWS Console you can either create a new virtual private cloud or use an existing one. You can choose an existing virtual private cloud and an existing subnet to ensure all virtual machines from your organizations are replicated in the same subnet.

  • Was this article helpful?