Skip to main content



How can we help you?


Druva Documentation

Backup servers with mixed workload (Backup sets)

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

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



Druva extends its backup capabilities for servers that run mixed workloads. With Druva, you can create multiple backup sets for the File, NAS Share, or MS-SQL server data for managing backups. 

You can configure different backup sets to back up different data. You can create one backup set to back up files and folders, and one or more backup sets to back up databases of standalone instances or availability groups. Different backup sets can use different backup content and backup policies with different backup schedules and retention periods. For example, you may want to retain financial files data residing on the server for five years and the HR files data for ten years. For databases, you may want to retain the employee database for ten years for compliance reasons inventory database for two years. In addition to these flexibilities, a backup set also enhances the backup performance by allowing multiple backup jobs to run simultaneously on a single server.


Druva exhibits the following behavior while configuring or during backup of the server that runs mixed backup sets:

  • You can now install and configure multiple services on the same server. For example, on a Windows server, you can configure HyperV, File server, MS-SQL server, and NAS, and run their individual jobs simultaneously. Similarly, on Linux, you can configure File server and NAS and run their individual jobs simultaneously.
  • The File server supports both content rule and custom content. The MS-SQL server supports only custom content.
  • A server can have one or many backup sets of type File or MS-SQL, which can be independently configured, backed up, restored, mapped to a storage, or mapped to a CloudCache.
  • You can add backup sets for the servers using Protect > File Servers.
  • The Backup Now option on the File Backup Sets page triggers a backup for the selected backup sets.
  • The Backup Now option (Registered Servers > Server details > Backup set under the Configured Backup Sets section > more options > Backup Now) triggers the backup for the selected backup sets configured for the server. 
  • You can individually enable or disable backup sets attached to a server.
  • Druva allows you to run multiple backups or restores, or multiple backups and restores simultaneously on the same server.
  • Druva creates restore points differently for the File and MS-SQL backup sets.
  • When a backup set is deleted, all the restore points corresponding to that backup sets are deleted.
  • If you delete the last File backup set attached to a server, the server is unconfigured from backup. The Configuration Status column in the Registered Servers screen displays Unconfigured.
  • You cannot delete a server until all its attached backup sets are deleted.

While configuring a File server or MS-SQL server policy for a mixed server, you must consider the following points:

  • You cannot configure an MS-SQL backup set to a server with Linux operating systems.
  • You cannot attach an MS-SQL backup set to a server with an unsupported Windows operating system. For more information about the supported operating systems, see Support matrix.


  • You cannot configure a server with multiple backup sets that have the same backup content.
  • A server cannot have more than one content rule with the same backup content applied to it.
  • Was this article helpful?