Skip to main content
Druva Documentation

System requirements for NAS devices

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Software requirements for NAS devices

Druva provides vendor-agnostic support for NAS devices. The supported protocol for SMB and NAS shares is as mentioned below. Phoenix can perform backup and restore provided your configuration adheres to the following  NAS proxy mappings.

Share type on the NAS device NAS device is mapped to Shares discovered
NFS Linux NAS proxy NFS
CIFS/SMB and NFS Windows NAS proxy CIFS/SMB
CIFS/SMB and NFS Linux NAS proxy NFS
CIFS/SMB and NFS Windows NAS proxy and Linux NAS proxy CIFS/SMB and NFS


  • The NAS proxy must be version  4.8.16-98358 or later for share auto-discovery to work. 
  • Phoenix validates the NAS device credentials before adding the NAS device. Ensure that you have valid device credentials.

Permissions for NAS share auto-discovery

The IPC$ share must be accessible with the provided device credentials. Phoenix accesses this share to authenticate itself with the NAS device, after which it can discover the other shares on the device.

Software requirements for NAS proxy

Since you install the NAS proxy on a Windows or Linux server, the server must comply with the following requirements.

Operating System


Support Considerations


  • Windows Server 2019 (64-bit)
  • Windows Server 2016 R2 (64-bit) 
  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2008 R2 (64-bit) 

Phoenix supports backup and restore from all SMB share versions supported on the respective Windows Server version.


  • CentOS 6.3,  6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, and 7.6 (64-bit)
  • Ubuntu 14.04, 16.04 , 18.04 LTS (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.4 , 7.5, 7.6, and 7.8  (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, 7.6, 7.7, and 7.8 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4 and 12.2 (64-bit)

Phoenix supports backup and restore from all NFS share versions supported on the respective Linux Server version and variants.

Hardware requirements

The following table describes the hardware specifications that the Phoenix agent requires to run one backup or restore job at a time:


Minimum Requirement


  • Three Cores or,
  • Three vCPUs if the agent is installed on a virtual machine


3 GB

Free space

  • On Windows and Linux servers, 2% of the total source data is utilized for the Phoenix application data. This application data is stored in the following locations:
    • Windows 2012 Server
    • Windows 2008 Server
    • Linux
      • /var/log/Phoenix
      • /var/Phoenix 

 By default, the Phoenix agent is configured to run three backup sets in parallel.

Ports and communication protocols for Phoenix

Phoenix communicates with your NAS shares to back up and restore the data. This occurs through ports and protocols that are secure for communication and transition of data. Phoenix uses Transport Layer Security (TLS) protocol to establish a connection and initiate communication between Phoenix components and your NAS device.

The following diagram depicts the ports and communication protocols that Phoenix uses for secure connection and communication during the backup and restore operations.