Disaster recovery support matrix, prerequisites, and limitations
Updated over a week ago

Enterprise Workloads Editions: ❌ Business | βœ… Enterprise(Purchase Separately) | βœ… Elite

πŸ“ Note
​Disaster Recoveryis supported on both, Public and Gov Cloud.

Support matrix

Disaster Recovery supports failover and failback on the following operating systems:

Operating system


File System

Partition Type

Windows (64-bit)

  • Microsoft Windows Server 2022 (Standard, Datacenter)

  • 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)



Primary/GPT/MBR/Dynamic disk

Linux (64-bit)

  • Red Hat Enterprise Linux (RHEL) 7.0- 9.0(BIOS)

  • CentOS 7.0-8.4 (BIOS), 7.4-8.4(UEFI)

  • Ubuntu 14.04, 16.04, 18.04, 20.04

  • SUSE Linux Enterprise Server 12 SP 3, 12 SP 5, 15.0 SP 2

  • Fedora: 30, 31, 32, 33

  • Oracle: 7.0-8.4 (BIOS), 7.5-8.4 (UEFI)



πŸ“ Notes

  • Windows:

    • Disaster Recovery does not support failback on the FAT and FAT 32.

    • Disaster Recovery does not support failback on the Extended partition on Windows.

    • Disaster Recovery supports failback on the Dynamic disk. During failback, Disaster Recovery converts the dynamic disk to basic disk.

    • ReFS is supported for failover. For failback, ReFS is converted to NTFS.

  • Linux:

    • Linux RAID configuration is not supported.

    • If you have RHEL 9.0 operating system installed, make sure you upgrade your vmware backup proxy to version 6.3.4-403650. Failing to do so may result in receiving an unsupported OS version warningduring failback checks.

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.medium , t2.large , t2.xlarge , t2.2xlarge

πŸ“ Notes

  • We've discontinued support for t2.micro and t2.small EC2 instance types for DR failovers. If you've selected t2.micro or t2.small instance types in the failover settings for virtual machines in existing DR plans, you must change the instance type to t2.medium or higher. These instances will automatically be upgraded to t2.medium if you run a DR failover without changing the instance type manually.

  • We recommend selecting the m5 or c5 instance type over the m4 or c4 instance type in the failover settings. If theAuto Assignfield is enabled in the failover settings, m5 or c5 instance type will be given precedence over the m4 or c4 instance type.

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

Disaster Recovery prerequisites if you are using Druva AWS proxy version 4.8.0 or later

  • Recommended instance types:
    While registering a Druva 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

    πŸ“ Note
    ​We recommend selecting the m5 or c5 instance type over the m4 or c4 instance type in the failover settings. If the Auto Assign field is enabled in the failover settings, m5 or c5 instance type will be given precedence over the m4 or c4 instance type.

Subnet prerequisite for Druva AWS proxy deployment

The Druva services should be available in the availability zone for the subnet that you intend to select during the Druva AWS proxy deployment. Perform the following tasks to determine if the chosen subnet can be selected for the Druva AWS proxy deployment or not.

  1. Copy the Druva backup service name that corresponds to the region where you intend to deploythe Druva AWS proxy from the following table:

    • ap-south-1:com.amazonaws.vpce.ap-south-1.vpce-svc-018246eb6465a0732

    • ap-east-1:com.amazonaws.vpce.ap-east-1.vpce-svc-0ca7ac8221c563a68

    • us-east-1:com.amazonaws.vpce.us-east-1.vpce-svc-0a9aa0b682d3a980d

    • ap-northeast-1:com.amazonaws.vpce.ap-northeast-1.vpce-svc-040be8f24b45eaf82

    • eu-west-1:com.amazonaws.vpce.eu-west-1.vpce-svc-0107991f549b4b600

    • ap-southeast-1:com.amazonaws.vpce.ap-southeast-1.vpce-svc-07babd8b6998f4a47

    • ca-central-1:com.amazonaws.vpce.ca-central-1.vpce-svc-0f00d5cda0c16b14d

    • ap-southeast-2:com.amazonaws.vpce.ap-southeast-2.vpce-svc-055b8fc235e64c402

    • us-west-2:com.amazonaws.vpce.us-west-2.vpce-svc-07023e0ed04c643fe

    • eu-north-1:com.amazonaws.vpce.eu-north-1.vpce-svc-0c7c6031bcbc8cdfa

    • us-gov-west-1:com.amazonaws.vpce.us-gov-west-1.vpce-svc-03c28740ddbae131f

    • us-west-1:com.amazonaws.vpce.us-west-1.vpce-svc-05274b103d6b1c796

    • eu-central-1:com.amazonaws.vpce.eu-central-1.vpce-svc-06a20c5470ce8207a

    • sa-east-1:com.amazonaws.vpce.sa-east-1.vpce-svc-02eaa75795ee6efc3

    • eu-west-2:com.amazonaws.vpce.eu-west-2.vpce-svc-04758dcfbe68314ca

    • eu-west-3:com.amazonaws.vpce.eu-west-3.vpce-svc-02d8fa4171c9495a2

  2. Log in to the AWS Management Console. Ensure you are logged into the region where you want to deploy the Druva AWS proxy.

  3. From the search bar at the top, search for and navigate to the VPC service.

  4. In the navigation pane on the left, under VIRTUAL PRIVATE CLOUD, click Endpoints.

  5. On the Endpoints page, click Create Endpoint.

    Create Endpoint.png
  6. On the Create Endpoint page, under the Service category click Find service by name.

  7. In the Service Name field, paste the service name that you copied in step 1. Click Verify.
    ​Note: After clicking Verify,you will see the service name not found error. This is because the Druva backup service hasn’t been created yet. It will be created as part of the Druva AWS proxy deployment. Ignore the message.

    Search for service availability.png


  8. In the VPC dropdown, select the VPC that you want to use for the Druva AWS proxy deployment. Ensure that the Druva service is available in the availability zone for the subnet that you intend to use. If the service is available in the availability zone, proceed with the Druva AWS proxy deployment. Else repeat the verification for an alternate VPC and a different subnet where the Druva service is available in the Availability Zone.

  9. In the Create Endpoint page, click Cancel.

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

Before you set up Disaster Recovery, 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 Druva 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.

Druva 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 Druva AWS proxy.

  • Disaster Recovery does not supportVMware Paravirtual SCSI.

DR Restore Limitations

During DR restore, Druva does not support custom tagging for writable snapshots that are being created.

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.

  • If the VM's firmware is UEFI, and if you have not upgraded your AWS and backup proxies to version 6.3.1 or later, then Failover EC2 instance with BIOS firmware will be launched by performing appropriate modifications on the disks.

  • You cannot select a VM if it is of UEFI firmware, and the source VM has a boot disk that is more than 2 TB in size or has more than 4 partitions in the boot disk.

  • AWS supports booting of the EC2 instance only in BIOS mode for the following operating systems even if the source VM might be of UEFI firmware in the vCenter. Druva does not support the failover conversion of such VMs.

    • RHEL 7.0 to 7.3

    • Centos 6.3 to 7.3

    • Oracle Linux 6.1 to 7.4

    • Suse linux 11 SP1 to 12 SP1

    • Ubuntu version below 14.04

    • For more information, see Key considerations.

Failback Limitations

  • Disaster Recovery does not allow you to resume failback on backup proxy with version earlier than 4.8.8_80128.

  • DR failbacks will fail if a VM had an NVMe controller or disk and was configured for DR.

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.

Did this answer your question?