Skip to main content

How can we help you?

Druva Documentation

File server backup workflow

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

 

This article provides the workflow diagrams and the steps for data backup from the following operating systems:

Note:  If you restart or reboot your servers during backups, the backup operation is aborted. Hybrid Workloads agent starts a fresh backup following the backup schedule. Alternatively, you can start a manual backup at any time. 

File servers with Windows operating system

This topic explains how data flow during data backup from the File servers with Windows operating system.

3.png

Backup workflow

Step Operation

Step 1

A backup request is initiated and forwarded to the Hybrid Workloads agent. 

Druva checks if Hybrid Workloads agent is running. 

  • If the agent is running, Druva performs the backup operation.
  • If the agent is not running, Druva performs the backup operation based on the type of backup job.
    • For a backup now job, Druva fails the backup request.
    • For a scheduled job, Druva waits until the expiry window of the backup request, else fails the backup request.

Step 2

Druva determines the type of backup.

If you or another administrator initiates the first backup, Druva performs a full backup. All subsequent backups triggered by administrators are incremental backups.

Step 3

 

Hybrid Workloads agent verifies that the VSS service is running. If the VSS service is not running, Hybrid Workloads agent starts the VSS service and instructs VSS to create a snapshot. 

Hybrid Workloads agent validates if snapshots are created successfully.

Step 4

Hybrid Workloads agent estimates the files and data to back up.

Step 5

 

  1. If snapshots are created successfully, Hybrid Workloads agent uses the VSS snapshots as the filesets for data backup to Druva Cloud.
  2. If the snapshots are not created successfully, Hybrid Workloads agent scans the live files and folders to create filesets for data backup to Druva Cloud.

Note: In case of VSS snapshots, Druva includes the locked files in the backup. However, in case of live folders and files scan, Druva considers locked files as missed files, and attempts to back up such files at the time of the next scheduled backup.

Step 6

After the backup completes, Hybrid Workloads agent deletes the created VSS snapshots.

File servers with Linux operating system

This topic explains how data flow during data backup from the File servers with Linux operating system.

4.png

Backup workflow

Step Operation

Step 1

A backup request is initiated and forwarded to the Hybrid Workloads agent.

Druva checks if Hybrid Workloads agent is running. 

  • If the agent is running, Druva performs the backup operation.
  • If the agent is not running, Druva performs the backup operation based on the type of backup job.
    • For a backup now job, queues the backup request. The backup request is executed after Hybrid Workloads agent starts.
    • For a scheduled job, skips the backup request.

Step 2

Druva determines the type of backup.

If you or another administrator initiates the first backup, Druva performs a full backup. All subsequent backups triggered by administrators are incremental backups.

Step 3

Hybrid Workloads agent performs the full scanning of live files and folders on the File server.

Step 4

Hybrid Workloads agent estimates the files and data to back up. 

Step 5

Hybrid Workloads agent uses the scanned folders and files as the fileset for data transmission. 

Note

  • Druva considers locked files as missed files, and attempts to back up such files at the time of the next scheduled backup. 
  • Druva supports valid UTF-8 encoded file names and filepaths. 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/FS/backup/<backupset_id> location.