Skip to main content

How can we help you?

Druva Documentation

NAS share backup workflow

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


This article provides the workflow diagrams and steps for data backup of NAS shares on Windows and Linux. 

Backup workflow

The following workflow illustrates the data flow during backup of NAS shares on Windows or Linux: 


The following table summarizes the workflow steps. 

Step Operation

Step 1

 A backup request is initiated and forwarded to the NAS proxy. 

Step 2


Druva Phoenix checks if the NAS proxy is running. 

  • If the proxy is running, Druva Phoenix performs the backup.
  • If the proxy is down, Druva Phoenix performs the backup based on the type of backup job, as specified below.
    • For a backup now job, Druva Phoenix queues the backup request. Druva Phoenix completes the request after the NAS proxy starts.
    • For a scheduled job, Druva Phoenix skips the backup request.

Step 3


Druva Phoenix determines the type of backup.

If it is the first backup from any source, Druva Phoenix performs a full backup. The subsequent backups are incremental backups.

Step 4

Phoenix agent performs a full scan of the files and folders on the NAS share.

Step 5

NAS proxy sends the scanned files and folders for backup to Druva Cloud.


  • If Druva Phoenix is unable to back up  locked files at the first attempt, it checks if the files are unlocked at the end of the backup. If the files are unlocked, they are backed up in the same backup cycle.  Locked files are not backed up.
  • Druva Phoenix supports valid UTF-8 encoded file names, filepaths, and share names. Files with filenames encoded in a format other than UTF-8 are skipped from backups.  You can find a list of all the skipped files  in the Phoenix-<job_id>-MissedFiles.log file at the  /var/log/Phoenix/NAS/backup/<backupset_id> location.
Step 6 NAS proxy transfers the deduplicated backup data to the Druva Cloud.