Skip to main content

How can we help you?

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. Druva 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
CIFS/SMB Windows NAS proxy CIFS/SMB
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

Note: 

  • The NAS proxy must be version  4.8.16-98358 or later for share auto-discovery to work. 
  • Druva Phoenix validates the NAS device credentials before adding the NAS device. Ensure that you have valid device credentials.
  • Druva Phoenix supports Amazon FSx for Windows and Amazon EFS shares for backups and restores. You can protect Amazon FSx shares using a Windows proxy, and protect Amazon EFS shares using a Linux proxy.  For more information see Druva Phoenix support for Amazon FSx for Windows and Amazon EFS

Permissions for NAS share auto-discovery

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

Least privileges to protect SMB shares on NetApp

In scenarios where one user account does not have all the required privileges over all folders in the SMB share hierarchy on a NetApp filer, ensure that the user account you use at the NAS device level has the least privileges summarized below for successful backups and restores.

Job Use account type Privileges
Backups Domain user or domain admin user User account must be a member of the Backup Operators group on the NetApp filer.
Restores Domain user or domain admin user

User account must have write permissions over the target location. 

Note:If the user account lacks write permissions over the target location, Druva Phoenix restores files with a .restored suffix at the target location. You need to rename these restored files by removing the suffix manually to complete the restore. The restore job ends with a Successful with Errors status.

Add this account to the credential store and assign it to the NAS shares. For more information, see Credentials in NAS share.

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

Edition

Support Considerations

Windows

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

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

Linux

  • 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, 7.6, 7.8, and 8.3 (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, ,7.8, and 8.3  (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, 7.6, 7.7, 7.8, and 7.9 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4 and 12.2 (64-bit)
  • Amazon Linux 2

Druva 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:

Hardware

Minimum Requirement

CPU

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

RAM

3 GB

Free space

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

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

Supported Encoding

Druva Phoenix supports valid UTF-8 encoded file names, filepaths, and share names.

Ports and communication protocols for Druva Phoenix

Druva 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. Druva Phoenix uses Transport Layer Security (TLS) protocol to establish a connection and initiate communication between Druva Phoenix components and your NAS device.

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

PortsAndCommunicationProtocols.png