Skip to main content
Druva Documentation

About Phoenix for File server

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


Managing the backup and recovery of the File servers in a distributed environment is usually a complex process involving multiple staff and complex infrastructure. Phoenix facilitates you by centralizing the backup and recovery of globally distributed File servers.

Phoenix uses server-side and client-side components to interact, manage, and control backups in your File servers.

Phoenix offers you a viable, cost-effective way of storing, managing, archiving, and recovering of your data on File servers that run on Windows and Linux platforms in your environment.  Phoenix supports backup and restore of the data deduplication-enabled volumes on Windows 2012 File server. Phoenix performs a non-optimized backup and restore in this case. Files on deduplication-enabled volumes are backed up as normal files and not as optimized files. Files backed up from deduplication-enabled volumes will be restored as normal files, even if restored to deduplication-enabled volumes.

Phoenix components for File server

The Phoenix components for a file server are:

Phoenix components for File server.png

  • Phoenix Cloud: Phoenix Cloud is the server component of Phoenix that authenticates and authorizes incoming backup and restore requests from Phoenix agent, installed on your File servers, and redirects it to Phoenix storage for fulfilling the requests.
  • Phoenix Management Console: Phoenix Management Console is a web-based, unified console that provides complete visibility and the high-level understanding of the health status of File servers that you manage, wherever those File servers reside.  You can globally view all your File servers located in your storage infrastructure,  discover File servers, and configure them for backup, recovery, and archival of data. It provides Phoenix administrators with an ability to –
    • Register and configure File servers for backup in their organization’s server infrastructure.
    • Control Phoenix activities by defining an administrative group, backup content, and backup policy.
    • Monitor backup and recovery jobs, activities, and reports.
  • Phoenix Agent: Phoenix agent is a client-side component, which is installed individually on each File server. You must deploy the Phoenix File server agent and register it to back up and restore File servers in your setup.
  • Phoenix CloudCache: Phoenix CloudCache is a dedicated server that temporarily stores backup and restores data from Phoenix agent.  At periodic intervals, Phoenix CloudCache synchronizes this data to Phoenix Cloud relaxing the bandwidth consumption in your infrastructure.

File types supported for backup

Phoenix provides defined file types that you can include in your backup or exclude from your backup. In the Create New Content Rule wizard, you can configure the Exclude file types and Include file types options in the content rule or custom content to exclude and include the required file types.

  • File types that are by default excluded: Video files, Audio file, All Executables, Image files. 

  • File types that are by default included: All Office files, PDF files, HTML files.

You can change the default selections by adding or removing the defined file types.

Phoenix also backs up and restores the Symlink and  Hardlinks file system objects. Note that only the link files are backed up and not the content of the files or directories they point to.

The following table lists the defined file types that you can use for including and excluding file types from the backup policy.

Defined 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, .jpe, .raw, .pic, .pct, .pxr, .sct, .ico, .PSD, .jpeg

HTML files

.html, .htm, .mht, .mhtml, .shtml

Audio files

.ogg, .mp3, .wav, .flac, .mpc, .au, .aiff, .aac, .m4a, .ra, .ape, .wma

PDF files


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

Archive Files .zip, .rar, .gz, .tgz, .bz, .bz2, .bzip, .bzip2, .gzip,. z, .tbz2, .iso, .7z, .cbr, .sitx, .tar.gz, .zipx
Backup Files .bak,  .old, .tmp
Data Files .sdf
DB files .db, .dbf, .pdb, .sql, .sqlite-wal
Developer files  .c, .class, .cpp, .cs, .dtd, .fla, .h, .java, .lua, .m, .mpp, .pl, .py, .sln, .swift, .vb, .vcxproj, .xcodeproj
Disk image files  .bin, .cue, .toast, .vcd
Font files .fnt , .fon , .ttf 
Game files   .b , .dem , .gam ,  .nes , .rom , .sav 
GIS files  .gpx , .kml , .kmz 
LOG files .log, .log1
OutLook files .pst, .ost, .prf, .msg
Plugin files .crx, .plugin
Setting files  .cfg, .ini
System files  .cab, .cur, .deskthemepack , .dmp , .icns , .lnk
Vector files   .ai ,  .eps , .ps , .svg 
Web files  .asp , .aspx , .cer , .cfm , .csr , .css , .dcr , .js , .jsp , .PHP, .rss 

Folders excluded from File server backup

By default, Phoenix excludes certain folders from File server backup. This is because, both Windows and Linux operating systems contain system-specific files, which can be excluded from backup. For example, the Recycle Bin on Windows servers contains files and folders that you previously deleted, so these files can be excluded from the backup.

The following table lists the folders that Phoenix excludes from backup. While creating a backup policy, these folders appear as excluded folders under the Exclude subfolders field.

Note: To include the folders that Phoenix excludes by default on the Backup Content tab, click the cross icon for the folder that you want to include.
Name of 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

Backup capabilities

Phoenix provides the following backup features for File servers. This section explains the various capabilities of a File server:

► Manual backup
During manual backups, Phoenix only backs up data that is defined in the backup policy. A manual backup is not restricted by the backup window that you have defined in the backup policy; it continues till all the data is backed up. In the event of a network connection failure during backup, Phoenix agent or backup proxy attempts to connect to Phoenix Cloud. After the connectivity is restored, backup starts from the state in which it was interrupted. A manual backup is not restricted by bandwidth, it uses maximum bandwidth available.
The Automatic Retry feature does not work with manual backups.
► Backup empty folders
From version 4.6.8 and later, Phoenix can back up and restore empty folders. After the upgrade,  the Windows File server agent where USN journal is enabled:
  • The empty folders created before the last backup and before the agent upgrade are not backed up. Contact Druva Support to back up these empty folders.
  • The empty folders created after the last backup but before the agent upgrade are backed up.

The Windows File server agent where UNC share is configured for backup, empty folders in the UNC share, created before and after the upgrade will be backed up and restored.

After the Linux File server agent upgrade, the empty folders created before and after the upgrade will be backed up and restored.

► Pre-backup and post-backup scripts
Phoenix allows administrators to configure File server agents to execute custom pre-backup scripts and post-backup scripts. Pre-backup scripts are executed before backup jobs to perform the specific pre-backup operation. Post-backup scripts are executed after backup jobs to perform the specific post-backup operation.  You can configure a backup policy with the settings for pre-backup and post-backup scripts to perform customer-driven processing tasks. For more information, see Pre backup and post backup scripts for File server.
► Backup servers with mixed workload (Backup sets)
Phoenix extends its backup capabilities for servers that run mixed workloads. This feature provides an ability to configure multiple backup sets of the File server and MS-SQL Database server for a single server. For more information, see Backup servers with mixed workload (Backup sets).
► Smart scan
Smart Scan uses heuristics to ensure that incremental backups are faster by optimizing the time it takes to scan files and folders. By default, the Smart scan option is disabled. You can enable this option while creating or editing a backup policy on the Backup Schedule tab. Here are the options that you can select while enabling Smart scan:
  • Skip ACLs for unmodified files from being scanned
  • Scan files and folders that are created or modified in the last x months. For example, 3 months.

Based on the options selected, Phoenix decides which files and folders need to be scanned during incremental backups. For more information, see:


  • Smart Scan is not needed for file systems that support USN Journal, such as NTFS and ReFS. When you enable the Smart scan option for NTFS or ReFS, Phoenix ignores the Smart scan flag in the configuration and displays the Smart scan is not needed for NTFS/ReFS message in the progress logs.
  • If you change the Backup Content setting under the backup set, the subsequent scan is a full scan.

For the frequently asked questions about Smart scan, see File server FAQs