Skip to main content

How can we help you?

Druva Documentation

DRaaS support matrix, prerequisites, and limitations

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


Support Matrix (Phoenix AWS proxy 4.8.0 and later)

If you have deployed backup proxy 4.8.0 and later, Phoenix DraaS supports failback on the following operating systems:

Operating system


File System

Partition Type

Windows (64-bit)

  • Microsoft Windows Server 2019 (Standard, Datacenter)
  • Microsoft Windows Server 2016 (Standard, Datacenter)
  • Microsoft Windows Server 2012 R2 (Standard, Datacenter)
  • Microsoft Windows Server 2012 (Standard, Datacenter)
  • Microsoft Windows Server 2008 R2 (Standard, Datacenter)
  • Microsoft Windows Server 2008 (Standard, Datacenter)





Primary/GPT/MBR/Dynamic disk

Linux (64-bit)

  • Red Hat Enterprise Linux (RHEL) 6.3, 6.9, 6.10 , 7.0 , 7.1-7.5, 8.0, 8.1, 8.2
  • CentOS 5.3, 5.11, 6.3, 6.9, 6.10 ,  7.0 , 7.1-7.5, 7.6, 7.7, 7.8, 8.0, 8.1, 8.2.
  • Ubuntu 14.04, 16.04, 18.04, 20.04
  • SUSE Linux Enterprise Server 11 SP 1 , 11 SP 4 , 12 , 12 SP 3 , 12 SP 5, 15.0 SP 2
  • Fedora: 30, 31, 32, 33
  • Oracle: 6 .10. 7.9, 8.2 (for both UEFI and BIOS)




  • Windows:

    • Phoenix DraaS does not support failback on the FAT and FAT 32.

    • Phoenix DraaS does not support failback on the Extended partition on Windows.

    • Phoenix DraaS supports failback on the Dynamic disk. During failback, Phoenix DraaS converts the dynamic disk to basic disk.

  • Linux:

    • Linux RAID configuration is not supported.

Supported AWS regions

To know the AWS regions that Druva supports for disaster recovery, see the Downloads page. 

In addition, AWS provides other regions that Druva can support for disaster recovery. For more information on regions that AWS provides, see Global Cloud Infrastructure. To know more about the regions that Druva can support for disaster recovery, but are not listed in the previous list, contact Support.

Supported AWS instance types

The following instance types are supported for failover. The instance types are displayed based on the region you have selected and the instances supported by Druva.

Instance Family Supported instance types

m4.xlarge, m4.large , m4.2xlarge , m4.4xlarge , m4.10xlarge , m4.16xlarge

m5.large , m5.2xlarge , m5.4xlarge , m5.10xlarge , m5.16xlarge

t2.micro , t2.small , t2.medium , t2.large , t2.xlarge , t2.2xlarge

Compute optimized

c4.large , c4.xlarge , c4.2xlarge , c4.4xlarge , c4.8xlarge 

c5.large , c5.xlarge , c5.2xlarge , c5.4xlarge , c5.8xlarge

Accelerated Computing  g3.4xlarge , g3.8xlarge , g3.16xlarge ,  g2.2xlarge , g2.8xlarge 
Memory optimized  r4.large , r4.xlarge , r4.2xlarge , r4.4xlarge , r4.8xlarge , r4.16xlarge 
Storage optimized

 d2.xlarge , d2.2xlarge , d2.4xlarge , d2.8xlarge ,

 i2.xlarge , i2.2xlarge , i2.4xlarge , i2.8xlarge ,

 i3.large , i3.xlarge , i3.2xlarge , i3.4xlarge , i3.8xlarge , i3.16xlarge

Phoenix DraaS prerequisites if you are using Phoenix AWS proxy version 4.8.0 or later

  • Recommended instance types:
    While registering a Phoenix AWS proxy, it is recommended that you select an instance type of size/family with the following minimum configuration: 8 CPUs, 16 GB memory, 3500 Mbps bandwidth, 10,000 IOPS. For example:

    • General purpose: m4.xlarge | m4.2xlarge | m4.4xlarge | m4.8xlarge | m4.10xlarge | m5.xlarge | m5.2xlarge | m5.4xlarge | m5.12xlarge | m5.24xlarge

    • Compute optimized: c5.2xlarge | c5.4xlarge | c5.9xlarge | c5.18xlarge | c5n.large 

  • You have set up the respective AWS Cloud/GovCloud account.

  • AWS account must have required permissions to create IAM Policy to delegate access to the AWS resources.

  • AWS account must have permissions to create multiple S3 buckets for each region.

  • Subnet entered in failover settings for each virtual machine should be able to reach AWS services like SQS and S3.

  • Security group should be selected appropriately if SSH/RDP is required.

  • All instances launched in public subnet must have a public IP address and the instances launched in private subnet must not have a public IP address.

  • Elastic public IPs should be selected based on available Elastic IPs in the AWS account.

  • Static private IP should be selected appropriately based on the subnet’s Classless Inter-Domain Routing (CIDR) block.

  • IAM role should have the same policies as that available on Phoenix Management Console.

  • VM should have a minimum of 1 GB free space on the boot partition.

  • If the VM has an outdated Kernel, it will be updated on failover.

Virtual machine prerequisites if you are using Phoenix AWS proxy version 4.8.0 or later

Before you set up Phoenix DraaS, go through the following:

  • In case of Linux virtual machines, if there are any devices in fstab mounted at the time of booting up, those devices will not be available in the EC2 instance created after failover.

  • Virtual machine must not have multi-boot partitions.

  • Virtual machine must not boot in the recovery mode.

  • Disks should be online and formatted for Windows.

  • Disks should be formatted and mounted for Linux.

  • "/" and "/boot" should be on the same disk for Linux.

Limitations (for Phoenix AWS proxy version 4.8.0 or later)

AWS Limitations

  • VMDK disk size should not be greater than 16TB - EBS volume supports up to 16TB.

Phoenix AWS proxy Limitations

  • The update DR copy job does not support restore of VM having the number of VMDKs more than 21. To be able to successfully restore a VM with 21 VMDKs ensure that only one update DR copy job is running on Phoenix AWS proxy.

Failover Limitations

  • DR failover does not support multiple NICs. Failover Instance will have only one NIC with Public-IP and Private-IP as configured in failover settings of the DR plan.
  • Failover for Windows 2008 non R2 will work only with t2  instance type. 

Failback Limitations

Phoenix DraaS does not allow you to resume failback on backup proxy with version earlier than 4.8.8_80128.

Windows Limitations

  • Windows Dynamic Disk as a boot partition is not supported.
  • Windows extended partitions are not supported.
  • Clustered drives are not supported: if your Windows Servers are a part of a cluster, exclude the clustered drive and perform the migration using the system drive only.

Linux Limitations

  • Linux LVM with extended partitions is not supported.
  • RAID configurations are not supported.
  • Was this article helpful?