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 apply to Phoenix DRaaS.

Phoenix limitations

  • You cannot identify the OS remote access and the checks for virtual machines deployed before the DRaaS release.
  • You can register one AWS account under one organization of a customer. You cannot share one AWS account 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 virtual machines having a GPT-partitioned boot disk.
  • 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.