Skip to main content

 

Druva Documentation

DRaaS limitations

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

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

Phoenix limitations

  • You cannot identify the OS remote access and checks for virtual machines that are deployed prior to the DRaaS release.
  • One AWS account can be registered under one organization of a customer. So, one AWS account cannot be shared between organizations of the same customer or different customer.
  • 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 GPT disks.
  • Disaster recovery restore fails for disk with REFS file system (Windows 2K12 and later).  AWS does not support REFS file system.
  • Windows Virtual Machine Import/Export supports 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 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 disks greater than 2 TB for disaster recovery as AWS supports only MBR.
  • For more information about limitations associated with AWS that are applicable to Phoenix DRaaS, see AWS Limitations.