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.
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.
Phoenix provides the following backup capabilities for NAS shares:
Auto-discovery of NAS shares
Phoenix initiates an automatic discovery of shares on the NAS device as soon as you add the NAS device. You can also use the Discover Shares option to run a share auto-discovery on demand. Share auto-discovery is particularly useful when the NAS device has a large number of shares and manual addition one by one is cumbersome. You can still add shares manually if required. The share auto-discovery process runs at 01:30 AM UTC every 24 hours. The frequency or time of NAS share auto-discovery cannot be altered.
The following table explains the mapping required between a NAS proxy and NAS device to discover SMB and NFS shares.
|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|
The Discover Shares feature will automatically discover shares only if your NAS device is mapped to a NAS proxy with a proxy version 4.8.16-98358 and later.
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.
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 is recommended if there are a lot of files on the NAS share that haven't changed recently. Smart Scan uses heuristics to detect such files and skips them from backups leading to faster incremental backups. After enabling Smart Scan, here are the options you can select:
Skip scanning ACLs or permissions for unmodified files
Only scan files created/modified in the last x months
Based on the options selected, Phoenix decides which files and folders need to be scanned during incremental backups.
- The Skip scanning ACLs or permissions for unmodified files option is applicable only for UNC share on Windows.
- If you change the Backup Content setting under the backup set, the subsequent scan is a full scan.
File types supported for backup
Phoenix provides defined file types that you can exclude from or include in your backups. Each file type is associated with specific extensions that are listed when a file type is selected. You can also enter custom extensions if you do not find your extensions under any predefined file type. You can remove extensions from a file type without removing the entire file type. You can also enter file patterns for exclusions or inclusions in your backups.
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, .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|
|Video files||.avi, .mpg, .mpeg, .divx, .rmvb, .wmv, .mov, .rm, .swf, .flv, .mkv, .3gp, .mp4|
.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|
|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|
Note: For content rules created post 21 Dec 2020, no files types are excluded or included by default until you choose the Specify File Exclusions or Inclusions option while creating or editing a content rule. Phoenix recommends and excludes some folders from backups by default. For more information, see the Folders excluded from NAS share backup section. The existing functionality remains the same for content rules created before 21 December 2020.
Content rules created on or after 21 December 2020 will no longer have the All Executables and All Office Files file types. The file type Executables will contain all extensions in the older Executables and All Executables file type. The file type Office Files will contain all extensions in the older All Office Files and Office Files file type. Content rules created before 21 December 2020 will continue using the older file types selected for inclusion or exclusion. For older content rules:
- If you had selected Office Files for inclusion or exclusion, the Content Rule details page and the Edit Content Rule page will show Office Files [-] under Included/Excluded File Types. Hovering over the [-] icon shows that the extensions that were earlier a part of the All Office Files file type have been removed.
- Similarly, if you had selected Executables for inclusion or inclusion, the Content Rule details page and the Edit Content Rule page will show Executables [-] under Included/Excluded File Types. Hovering over the [-] icon shows the extensions that were earlier a part of the All Executables file type have been removed.
- If the older content rule was using All Executables and All Office Files, the Content Rule details page and the Edit Content Rule page would show Executables and Office Files.
Note: The extensions that were included or excluded in the older content rules will remain unchanged despite the change in the 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.
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|