Skip to main content
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 Phoenix AWS proxy 4.8.0 and later, Phoenix DRaaS supports failover on the following operating systems:

Operating system

Editions

File System

Partition Type

Windows (64-bit)

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

NTFS

 

 

Primary/Extended/Dynamic (data disk only)

Linux (64-bit)

  • Red Hat Enterprise Linux (RHEL) 6.3, 6.9, 6.10 [RM], 7.0 [RM], 7.1-7.5
  • CentOS 5.3, 5.11, 6.3, 6.9, 6.10 [RM],  7.0 [RM], 7.1-7.5
  • Ubuntu 14.04, 16.04
  • SUSE Linux Enterprise Server 11 SP 1 [RM], 11 SP 4 [RM], 12 [RM], 12 SP 3 [RM]

EXT2/EXT3/EXT4/XFS

Primary/Extended

Notes

  • Windows:

    • Phoenix supports disaster recovery of virtual machines with BIOS system initializer only. Unified Extensible Firmware Interface (UEFI) is not supported.

    • GPT based primary partition is not supported for disaster recovery.

    • Virtual disks alone are not supported for disaster recovery.

    • Extended partition is not supported for failover.

    • Phoenix DRaaS does not support failover on the FAT, FAT 32, and ReFS file systems. 

  • Linux:

    • Linux RAID configuration is not supported.

    • Phoenix supports disaster recovery of virtual machines with BIOS system initializer only. Unified Extensible Firmware Interface (UEFI) is not supported.

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

Operating system

Editions

File System

Partition Type

Windows (64-bit)

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

NTFS

 

 

Primary/GPT/MBR/Dynamic disk

Linux (64-bit)

  • Red Hat Enterprise Linux (RHEL) 6.3, 6.9, 6.10 [RM], 7.0-7.5
  • CentOS 5.3, 5.11, 6.3, 6.9, 6.10 [RM],  7.0 [RM], 7.1-7.5
  • Ubuntu 14.04, 16.04
  • SUSE Linux Enterprise Server 11 SP 1, 11 SP 4, 12, 12 SP 3

EXT2/EXT3/EXT4/LVM/XFS

Primary/Extended

Notes:

  • Windows:

    • Phoenix DRaaS does not support failback on the FAT, FAT 32, and ReFS file systems. 

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

    • Phoenix DRaaS supports failback on the GPT based partition, however, the GPT disk gets converted to the MBR partition.

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

    • Phoenix supports disaster recovery of virtual machines with BIOS system initializer only. Unified Extensible Firmware Interface (UEFI) is not supported.

  • Linux:

    • Linux RAID configuration is not supported.

    • Phoenix supports disaster recovery of virtual machines with BIOS system initializer only. Unified Extensible Firmware Interface (UEFI) is not supported.

Supported AWS regions

Druva supports the following AWS regions for disaster recovery:

  • AWS GovCloud (US West)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • EU (Ireland)

  • EU (Frankfurt)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • South America  (Sao Paulo)

  • Canada (Central)

  • EU (London)

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 Druva Support.

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

  • Recommended instance types:

    • 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 

      For the other instance types, select EC2 instance having a minimum 8GB RAM to create Phoenix AWS proxy. 

  • 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.
  • Update DR copy job fails if VMDK was excluded at the time of VM backup.
  • Update DR copy job fails if the VM uses EFI/UEFI as its system initializer firmware.

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.  

Failback Limitations

Phoenix DRaaS does not allow you to resume the failback operation.

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 GPT is not supported.
  • Linux LVM with extended partitions is not supported.
  • RAID configurations are not supported.

Support Matrix (Phoenix AWS proxy 4.7.6 or earlier)

If you have deployed Phoenix AWS proxy 4.7.6 or earlier, Phoenix supports the following operating systems for disaster recovery (DR).

Operating system

Editions

Windows (32-bit and 64-bit)

  • Microsoft Windows Server 2012 R2 (Standard, Datacenter, Enterprise)
  • Microsoft Windows Server 2012 (Standard, Datacenter, Enterprise)
  • Microsoft Windows Server 2008 R2 (Standard, Datacenter, Enterprise)
  • Microsoft Windows Server 2008 (Standard, Datacenter, Enterprise)
  • Microsoft Windows 7 (Professional, Enterprise, Ultimate)
  • Microsoft Windows 8 (Professional, Enterprise)
  • Microsoft Windows 8.1 (Professional, Enterprise)

Linux (64-bit)

  • Red Hat Enterprise Linux (RHEL) 5.x, 6.x, 7.0-7.2
  • CentOS 5.x, 6.x, 7.0-7.2
  • SUSE Linux Enterprise Server 11, 12
  • Ubuntu 12.x, 13.x, 14.x, 15.x
  • Oracle Enterprise Linux 5.x, 6.x, 7.x
  • Fedora Server 19-21
  • Debian 6.0.0-6.0.8, 7.0.0-7.8.0, 8.0.0

Supported AWS regions

Druva supports the following AWS regions for disaster recovery:

  • AWS GovCloud (US West)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • EU (Ireland)

  • EU (Frankfurt)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • South America  (Sao Paulo)

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 Druva Support.

Phoenix DRaaS prerequisites if you are using Phoenix AWS proxy version 4.7.6 or earlier

Before you set up Phoenix DRaaS, ensure the following:

  • Virtual machine Import/Export supports importing Windows instances into the most instance types. However, you can import the Linux instances into the following instance types:

    • General-purpose: t2.micro | t2.small | t2.medium | m3.medium | m3.large | m3.xlarge | m3.2xlarge

    • Compute-optimized: c3.large | c3.xlarge | c3.2xlarge | c3.4xlarge | c3.8xlarge | c1.4xlarge

    • Memory-optimized: r3.large | r3.xlarge | r3.2xlarge | r3.4xlarge | r3.8xlarge

    • Storage-optimized: i2.xlarge | i2.2xlarge | i2.4xlarge | i2.8xlarge

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

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

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

Virtual machine prerequisites if you are using Phoenix AWS proxy version 4.7.6 or earlier

Before you set up Phoenix DRaaS, ensure the following:

  • Virtual machine Import/Export supports VMware virtual machines only

  • For virtual machine Import/Export, you import Windows and Linux instances with the following file systems:

    • Windows (32 bit and 64 bit): MBR-partitioned volumes that are formatted using the NTFS file system. GUID Partition Table (GPT) partitioned volumes are not supported.

    • Linux (64 bit): MBR-partitioned volumes that are formatted using the ext2, ext3, ext4, Btrfs, JFS, or XFS file system. GUID Partition Table (GPT) partitioned volumes are not supported.

  • In case of Linux virtual machines, if there are any devices in fstab mounted at the time of booting up, ensure that you mount devices using the UUID rather than the device name.

  • Virtual machine must not have multi-boot partitions.

  • Virtual machine must not boot in the recovery mode.

  • You must enable RDP/SSH in the firewall setting. Before performing DRaaS, enable the remote desktop connection in Windows and SSH in Linux.

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

  • VMware tools service startup type should be manual.

  • Disconnect any CD-ROM drives.

  • Windows virtual machines should use volume licensing.

Limitations (for Phoenix AWS proxy version 4.7.6 or earlier)

This topic lists the Phoenix limitations and AWS limitations that apply to Phoenix DRaaS.

Phoenix limitations

  • You cannot identify the OS remote access and the checks for virtual machines deployed before the DRaaS release.
  • We do not recommend using CloudCache for virtual machines configured for disaster recovery.

AWS limitations

Phoenix DRaaS uses AWS import service to convert the virtual machines backup images to AMIs.

  • AWS does not support import image operations for virtual machines having a GPT-partitioned boot disk.
  • AWS  VM import/export does not support image operations for virtual machines having UEFI partition disks. 
  • Disaster recovery restore fails for a disk with REFS file system (Windows 2K12 and later).  AWS does not support REFS file system.
  • Windows Virtual Machine Import/Export supports the MBR-partitioned volumes that are formatted using the NTFS file system. GUID Partition Table (GPT) partitioned volumes are not supported.
  • Linux Virtual Machine Import/Export supports the MBR-partitioned volumes that are formatted using ext2, ext3, ext4, Btrfs, JFS, or XFS file system. GUID Partition Table (GPT) partitioned volumes are not supported.
  • AWS does not support bootable disks greater than 2 TB for disaster recovery due to MBR limitations. AWS supports only the MBR-partitioned bootable disks.

For more information about limitations associated with AWS that apply to Phoenix DRaaS, see AWS Limitations.