Skip to main content
Druva Documentation

About Phoenix for NAS shares

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

Phoenix offers you a viable, cost-effective way of storing, managing, archiving, and recovering your data on NAS devices. The key highlights of the Phoenix support for NAS devices are as follows:

  • Scale-out NAS agent that allows parallel and performant backups for large NAS deployments.
  • Smart scan approach, including machine learning through metadata analysis that identifies data that has changed for backup versus repeatedly backing up all data regardless if it has changed or not. By focusing on backing up only the new or changed data, backup cycles are dramatically shortened.

  • Native data format and vendor agnostic approach that enables device migration and data intelligence use cases.

Phoenix components 

The Phoenix components of NAS shares are:

  • Phoenix Cloud: This is the server component of Phoenix that authenticates and authorizes incoming backup and restore requests from the NAS proxy. The NAS proxy is installed on a separate Windows or Linux server and redirects the requests to the Phoenix storage.
  • Phoenix Management Console: The Phoenix Management Console is a web-based, unified console that provides complete visibility and understanding of the health status of the NAS devices and its shares that you manage, wherever those NAS devices reside.  You can globally view all of the NAS devices located in your storage infrastructure and configure NAS shares for backup, recovery, and archival of the data. The console provides Phoenix administrators with an ability to:
    • Register and configure NAS devices and shares for backup in the server infrastructure of the organization.
    • Control Phoenix activities by defining backup content, backup policy, retention period, and more.
    • Monitor backup and recovery jobs, activities, and reports.
  • NAS proxy: The NAS proxy is the Phoenix Agent installed on a Windows or Linux server, which handles the backup and restore requests from the NAS shares. You need to install and activate the NAS proxy to establish its connectivity with Phoenix. The link between Phoenix and a NAS device is established when you map an activated NAS proxy to a NAS device. You can map multiple proxies to a device and can also attach it to multiple backup sets. 
  • Phoenix CloudCache:  The Phoenix CloudCache is a dedicated server that temporarily stores backup and restore data from the NAS shares.  At periodic intervals, Phoenix CloudCache synchronizes this data to the Phoenix Cloud and reduces the bandwidth consumption within your infrastructure.

Backup capabilities

Phoenix provides the following backup capabilities for NAS shares:

Manual backup 

During manual backups, Phoenix only backs up data as defined in the backup policy. The backup window defined in the backup policy does not restrict a manual backup. Instead, it continues until all the data is backed up. In the event of a network connection failure during backup, the NAS proxy attempts to connect to the Phoenix Cloud. After the connectivity is restored, backup resumes from the state in which it was interrupted. Network bandwidth does not restrict a manual backup, as it uses the maximum bandwidth available. Note that the Automatic Retry feature does not work with manual backups.

Back up empty folders 

Phoenix can back up and restore empty folders. On SMB shares, the USN journal must be enabled to back up and restore an empty folder.

Smart scan

The Smart scan feature optimizes scan duration at the time of executing a backup job. Phoenix can save a lot of time if certain files and folders, or Access Control Lists are not scanned at the time of backup. The Smart scan feature provides options that let you choose what should be skipped when Phoenix scans files and folders for backup.  After you enable Smart scan:

  • You can choose to skip Access Control Lists (ACLs) from getting scanned.
  • You can choose to not to scan folders that are not modified for a specified period for backup, for example, three months.

By default, the Smart scan option is disabled. You can enable this option while creating or editing a backup policy. For more information, see: Manage backup policies.


  • The Skip ACL scan for unmodified files option is not applicable for Linux servers. 
  • First backup after a change in the content specified in the backup policy will be a full scan. The subsequent scans will be as per configuration.

File types supported for backup

While configuring a new backup set, you can configure the Exclude file types and Include file types options.

The file types that are excluded by default are video files, audio files, All Executables, and image files. The file types that are included by default are All Office files, PDF files, and HTML files. You can change the default selection of the file types.

The following table lists the file types that you can include and exclude from the backup policy.

File types File extensions
Office files

.doc, .ppt, .xls, .docx, .docm, .xlsx,
.xlsm, .xts, .xltm, .pptx, .pptm, .odt, .odb, .ods, .odp, .odg, .odc, .odf, .odi, .odm, .ott, .ots, .otp, .otg, .otc, .otf, .oti, .oth, .txt, .adp, .adn, .accdb, .accdr, .accdt, .accde, .dotx, .xltx, .mdb, .mda, .mdt, .mdw, .mdf, .mde, .mam, .maq, .mar, .mat, .maf, .ppl 

All Office files

.doc, .ppt, .xls, .docx, .docm, .xlsx, xlsm, .xts, .xltm, .pptx, .pptm, .odt, .odb, .ods, .odp, .odg, .odc, .odf, .odi, .odm, .ott, .ots, .otp, .otg, .otc, .otf, .oti, .oth, .txt, .adp, .adn, .accdb, .accdr, .accdt, .accde, .dotx, .xltx, .mdb, .mda, .mdt, .mdw, .mdf, .mde, .mam, .maq, .mar, .mat, .maf, .ppl, .mpt, .xlt, .vdx, .vssm, .vsdx, .vsdm, .vtx, .xsn, .one, .pot, .vsd, .dotm, .vsl, .vsw, .vst, .vss, .vsx, .dot, .potm, .vssx, .potx, .vstm, .pub, .vstx

Image files .gif, .jpg, .bmp, .png, .tif, .jpeg, .raw, .pic, .pct, .pxr, .sct, .ico, .PSD
HTML files .html, .htm, .mht, .mhtml, .shtml
Audio files .ogg, .mp3, .wav, .flac, .mpc, .au, .aiff, .aac, .m4a, .ra, .ape, .wma
PDF files .pdf
Video files .avi, .mpg, .mpeg, .divx, .rmvb, .wmv, .mov, .rm, .swf, .flv, .mkv, .3gp, .mp4

.exe, .dll, .msi, .com, .drv, .sys, .cpl, .ocx, .msp

All Executables

.exe, .dll, .msi, .com, .drv, .sys, .cpl, .ocx, .msp, .exec, .osx, .ps1, .sh, .bat, .cmd, .app, .dmg, .pkg, .rpm, .deb

Folders excluded from NAS share backup

By default, Phoenix excludes certain folders from the NAS share backup, since both Windows and Linux operating systems contain system-specific files, which can be excluded from backup. For example, the Recycle Bin on the Windows server contains deleted files and folders, which won't require backup.

The following table lists the default folders that Phoenix excludes from the backup. 

Operating system Folder names



  • Recycle Bin
  • Program Files
  • Program Files (x86)
  • Program Data
  • Recovery
  • System Volume Information
  • Windows 
  • Recycler



  • proc
  • sys
  • dev
  • tmp
  • lost+found
  • var/Phoenix 
  • /etc/Phoenix 
  • /selinux