Skip to main content

 

Druva Documentation

DRaaS FAQs

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

Questions

►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.


►How much time will take to recover a virtual machine in the AWS account as an EC2 instance?

It depends on the factors such as the virtual machine, guest operating system, and the Kernel version of the guest operating system, the presence of applications installed on the virtual machine etc. On an average, it takes 10-30 minutes to recover a virtual machine as an EC2 instance. It can take up to 60 minutes to recover a virtual machine in some cases, such as if you are using:

  • An AWS free tier account, or
  • A Phoenix evaluation license

►What is the expected RPO of Phoenix DRaaS?

The expected RPO largely depends on the time it takes to complete a backup job and then a DR restore/update DR copy job. In case you have scheduled to run a DR copy update immediately after the backup job, the RPO for DR would be the sum of the backup time and the time to complete the DR job. In general, Phoenix DRaaS is best suited for VMs with a few hours plus RPO.


►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, the cost of creating a DR 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 DR copies for virtual machines and maintains them in the AWS account. At the time of disaster, you can launch EC2 instance from the latest DR copy, in-turn spinning up to production in minutes.


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

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


►Does Phoenix overwrite a DR copy on every DR cycle?

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


►Can I access a DR copy after an instance is launched for disaster recovery?
Yes. If an instance is launched from a DR copy for disaster recovery, we do not delete it. However, you cannot start an EC2 instance from your AWS account using the DR copy. To start an EC2 instance, you have to run a failover job from the Phoenix Management Console.

►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.


►What AWS regions does Druva support for disaster recovery?

Druva supports the following regions for disaster recovery:

  • AWS GovCloud
  • US East (N. Virginia)
  • US West (N. California)
  • US West (Oregon)
  • EU (Ireland)
  • EU (Frankfurt)
  • Asia Pacific (Mumbai)
  • Asia Pacific (Tokyo)
  • Asia Pacific (Singapore)
  • Asia Pacific (Sydney)
  • South America  (Sao Paulo)
 
►Can I configure a virtual machine to replicate data in any AWS region?

No. By default, Phoenix replicates data and creates a DR copy in the same region where you back up the virtual machines. Phoenix DRaaS requires you to deploy at least one Phoenix 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.
  • Phoenix AWS Proxy deployed and activated to perform the data decryption and DR copy creation. 
  • Permissions in the form of an IAM Role and IAM Policy for the DR Proxy to perform create a DR copy from the virtual machine snapshot and store it in the customer account. Phoenix AWS Proxy uses this DR copy to start an EC2 instance. 

►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.

Orchestration Questions


►What type of EBS volume is used for DR restores?

Phoenix uses the GP2 type.


►Does the failover process resume if a Phoenix AWS proxy shuts down during the process of failover?

Yes, the failover operation is resumable, however, you cannot resume the restore operation. With orchestration, Phoenix provides an option to continue the failover of the other virtual machines, if one or some fails. The information to resume a failover is maintained in the s3 bucket and based on the data the virtual machine failover is either skipped if is done already or is performed for the virtual machine.


►Does the DR restore resume if there is a network disconnect or an agent restart?

Yes, the DR restore resumes on a network disconnect, but the job fails if the agent restarts.


►Do we store only the logs in the customer AWS account in the S3 bucket?

The customer AWS account stores logs specific to the DR restores and the metadata information for failover in the S3 bucket.


►If a boot order is specified for virtual machines and a virtual machine error out on a failover, does Phoenix proceed with failover of the next virtual machine?

The failover of all virtual machines in a boot step starts in parallel. Phoenix provides an ability to configure failover settings to abort or continue the failover at the step level upon failure of a virtual machine.


►Can I update my existing IAM policy for the Phoenix AWS proxy?

Yes, you can update the existing DruvaIAMPolicy in your AWS account. To update the policy, perform the following steps:

  1. On the AWS Management Console, select the Services tab and click IAM.
  2. In the left pane, click the Roles tab.
  3. On the Roles page, type DruvaIAMRole in the search box.
  4. Click the DruvaIAMRole role to view the role details.
  5. On the Summary page, click the Permissions tab.
  6. In the Permissions policies section, click the DruvaIAMPolicy option.
  7. On the Edit DruvaIAMPolicy page, click the JSON tab, copy the policy content in the editor from the policy document, and click Review policy.
  8. Click Save changes.
  • Was this article helpful?