Skip to main content
Druva Documentation

Backup servers with mixed workloads (Backup set)

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

​​​​Overview

Phoenix extends its backup capabilities for servers that run mixed workloads. With Phoenix, 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.

Behavior

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

  • You can 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 and NAS server support 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 instances and AGs using Protect > MS-SQL Servers.
  • The Backup Now button on the Availability group or instance details page triggers the backup for the individual backup set configured for the selected instance or AG.
  • You can individually enable or disable backup sets attached to the instance or AG.
  • Phoenix allows you to run multiple backups or restores, or multiple backups and restores simultaneously on the same server.
  • Phoenix 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 backup set attached to an instance or AG, the instance or AG is unconfigured from backup. The Configuration Status column on the Instances/AGs tab displays the cross.png icon.
  • You cannot delete an instance or AG 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 having agent version 1.x.
  • 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 unsupported Windows operating system. For more information about the supported operating systems, see Support matrix.

Limitations

  • When you filter servers using the Last Backup Status filter, the result lists down all the instances and AGs of the servers for which that status is available, even if the other backup policy type for the instances or AGs have different statuses. For example, if you filter servers using the Successful status, the result lists the servers with Successful status. Additionally, for those instances and AGs, it will also list the other statuses, such as Failed, Successful with errors, and so on.
  • You cannot configure an instance or AG with multiple backup sets that have same backup content.
  • You cannot select the instance(s) and AG(s) together to create SQL backup sets at the same time.
  • An instance or AG cannot have more than one content rule with the same backup content applied to it.