Skip to main content
Druva Documentation

Configure servers to back up data from multiple workloads

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

Phoenix allows you to back up servers that run mixed workloads. You can configure multiple dataset backups of the File and MS-SQL server on a single server. After you have created one File or MS-SQL backup set, you can add another File or MS-SQL backup set to the configured server. However, you can create only one MS-SQL backup set per instance or AG. Phoenix offers the flexibility to independently configure, back up, and restore the backup sets. 

After you register a File server, you can see it under the All Servers tab on the Windows/Linux Servers page. The Phoenix agent discovers the standalone instances and availability groups (AG) running on the MS-SQL server and lists the instances and AGs under the Instances/AGs tab on the MS-SQL page. 

To configure a server running mixed workloads for backup, perform the following steps:

  1. Create a File backup set.
  2. Create an MS-SQL backup set for an instance.
  3. Create an MS-SQL backup set for an availability group.

Create a File backup set

Backup set allows you to define the content to back up and the backup schedule for the server. Before creating a backup set, ensure that you have associated the server with the administrative group. To create a File backup set, perform the following steps:

Note: Phoenix displays the Assign Administrative Group page only if the server associated with the selected standalone instance or AG is not mapped to any administrative group.

Step 1: Attach server to an administrative group

An administrative group allows you to logically categorize your servers for better management. Before creating a backup set, you must first attach the server to the administrative group.

To attach File server to an existing administrative group

  1. Log on to Phoenix Management Console, select your organization from the menu bar at the top, and click Protect > Windows/Linux Servers.
  2. Under the All Servers tab on the Windows/Linux Servers page, configure servers as follows:
    • For single-server configuration: Select your server and click Create File Backup Set. The Create File Backup Set: Assign Administrative Group wizard opens.
    • For multi-server configuration: Select your servers and click Configure Server(s) for Backup. The Create File Backup Set: Assign Administrative Group wizard opens.
  3. From the Administrative Group drop-down list, select the required administrative group, and click Next: Create Backup Set. For more information about creating a backup set for your server, see Create File backup set.

Note: Phoenix provides the Default Administrative Group without any servers attached to the group.

To attach File server to a new administrative group

  1. Click Create New Group adjacent to the Administrative Group drop-down list.
  2. The Create New Administrative Group window opens.
  3. In the Name box, type the name of the administrative group.
  4. In the Description box, type a description for the administrative group.
  5. Click Save.
    The administrative group created now appears in the Administrative Group drop-down list on the Create File Backup Set: Assign Administrative Group wizard.
  6. From the Administrative Group drop-down list, select the new administrative group, and click Next: Create Backup Set .

Step 2: Create a File backup set

  1. Define backup content for your File server as follows:
    1. Under the Storage & Backup Content tab, provide the following information:
Field Description
Storage Select the Phoenix storage where the backed up data of the File server is stored.

Select Content

 

Click one of the following options to select the content rule for your File server.

  • Use Content Rule: Click the Use Content Rule option to use an existing predefined content rule to back up files and folders on your File server. When you select an existing content rule, the summary of the selected content rule is displayed under the Select Content section.
    File_backup_content_rule_Mixed_Workload.PNG
     
  • Custom Content: Click the Custom Content option to create a new content rule to back up files and folders on the File server. Provide the following information to create custom content:
    File_backup_custom_content_Mixed_Workload.PNG
    Field Description
    All folders Select this option if you want to backup all the folders.

    Specific folders

    Select this option to backup a specific folder. Click the Browse icon.png  browse icon to browse the folder on your system or type the absolute path of the folder in the corresponding box, and click Add

    The folder path that you add appears in the box under the Add option. 

    To exclude any folder paths that are added for backup, click the delete icon next to the folder path in the box under Add

    Note: In case of the multi-server configuration, you cannot browse folder to select folder for backup.

    Exclude file types

    Select this option to exclude certain files from the backup.

    In the box below the option, select the file types that you want to exclude. 

    Note: If you selected Exclude file types, click More file extensions to exclude to provide the file extensions that you do not see in the default file type list. Type an extension preceded by an asterisk (*), for example, *.dotm. Separate consecutive entries using a comma.

    Example: Consider you have 100 files (Textdata1.txt to Textdata100.txt) stored on your system. To exclude all the files. click More file extensions to exclude and enter "Text*.txt ".

     Include file types

    Select this option to backup specific files.
    In the box below the option, select the file types that you want to include for backup. 

    Note: If you selected Include file types, click More file extensions to include to provide the file extensions that you do not see in the default file type list. Type an extension preceded by an asterisk (*), for example, *.dotm. Separate consecutive entries using a comma. 

    Exclude subfolders

    Use this option to exclude subfolders from backup. Type the relative or absolute path to the folder in the box under Exclude subfolders option, and then click Add.

    Note: If you are configuring Linux servers, exclude cgroups from backup. 

    To include the folders that are excluded from backup by default, click the delete icon next to the folder name in the box under Exclude subfolders

    Click Save as New Content Rule. The custom content rule created now appears in the Use Content Rule drop-down list. Select the content rule from the Use Content Rule drop-down list.

  1. Under the Backup Policy tab, attach the backup policy to the server. It is possible to create backup policies for File server and MS-SQL server with the same name. You can attach your File server to an existing backup policy or create a new backup policy and attach it to the server.

Step 1: Provide backup policy summary details

  1. Under the Summary tab, provide the following information:
    • Name: The name for the backup policy that you want to create.
    • Description: A short description of the backup policy. 
  2. Click Next to define the backup schedule.

Step 2: Define a backup schedule

  1. Under the Backup Schedule tab, provide the following information:
    Field Description

    Ignore backup duration for first backup

    The option to ignore the specified backup duration for the first backup job.

    You can disable this option to enforce backup duration for the first backup job.

    Automatic Retry

    The option to define the automatic retrial options for backup. For more information, see  Backup retry.

    Note: If you do not want to define the automatic retrial options, clear the Automatic Retry check box.

    Max number of retries

    In an active schedule window, the maximum number of retry attempts for a job. By default, the field is set to 2 attempts.

    Wait interval before each retry

    The wait interval between each retry. By default, the field is set to 10 minutes.

    Enable Smart Scan

    Smart scan optimizes the scanning duration for backup. You can enable or disable the Smart scan option for the selected backup schedule. 

    When you enable smart scan, you can use the following options to optimize scan duration:

    • Skip ACL scan for unmodified files
      Scanning Access Control Lists consumes a lot of time. Enable this option to skip ACL scanning for files that are not modified. 
    • Only scan files created/modified in the last <number of> months
      If files are not modified for a long period, enable this option to let Phoenix skip the unmodified files. You can choose: 
      • 3, 6, 9, or 12 months as the time period of unmodified or created files. One month here is an equivalent of 30 days. For example, if you select 3 months, Phoenix skips scanning files and folders that were not modified or created in the last 90 days.
    • Full backup schedule
      Even if you enable smart scan, you can still run a full scan. You can choose to run a full scan every 24 weeks or less. We recommend that you run a full scan every 4 weeks.In addition, specify the preferred day, time, duration, and bandwidth.

    See also, File Server FAQs.

    Note:
    • ACL scan is not applicable for Linux servers.
    • Smart scan is not applicable for NTFS.
    • If you change the backup content in the backup policy, all subsequent scans will be full scans.
  2. Click Next to define the retention details.

Step 3: Define retention

  1. Under the Retention tab, provide the following information.
    Default_retention_policy_file.PNG 
    Field Description

    All snapshots for

    The duration for which you want to retain all snapshots.

    Weekly revisions for

    The duration for which you want to retain weekly snapshots.

    Monthly revisions for

    The duration for which you want to retain monthly snapshots.

    Yearly revisions for

    The duration for which you want to retain yearly snapshots.

Note: Ensure that you enter a value in at least one of the fields. Phoenix treats the values in the empty fields as zero. 

  1. Click Next to define the pre and post script settings.

Step 4: Define pre and post script settings

You can optionally define settings for executing the pre-backup and post-backup scripts on Windows or Linux server. For more information about pre-backup and post-backup scripts, see Pre and post-backup scripts for File server.
Procedure

  1. Under the Pre/Post Script settings tab, provide the following information:

    Pre_post_backup_script.jpg
    Field Description

    Enable scripts for Windows servers  

    Select this check box to enable the execution of pre and post backup scripts on Windows server. When you select the check box, the Specify scripts location field gets enabled.

    Specify scripts location

    Specify the folder path containing the pre_script.bat and post_script.bat backup scripts.

    Enable scripts for Linux servers 

    Select the Enable scripts for Linux servers check box to enable the execution of pre and post backup scripts on Linux server. When you select the check box, the Specify scripts location field gets enabled.

    Specify scripts location

    In the Specify scripts location field, specify the folder path containing the pre_script.sh and post_script.sh backup scripts.

    Skip backup if

    Select one of the following options.

    • Pre-script is not present at the specified location
    • Pre-script execution fails

    Pre-script is not present at the specified location

    Select this option to skip the backup operation when the pre-backup script is unavailable at the location specified in the Specify scripts location field.

    Pre-script execution fails

    Select this option to skip the backup operation when the pre-backup script execution fails.

    Abort pre/post script execution if it does not complete in XX Hours/Minutes Specify the time in hours or minutes after which the backup script execution aborts. If the script execution time limit is not specified,  the pre-backup and post-backup scripts run until the script execution is complete or 1 year, whichever is less. 
  2. Click Create.
    The created backup policy is listed in the Backup Policy drop-down list. 
  3. Under the Policy Details section, verify the configuration summary of the new backup policy, and click Finish. 

The server configured for backup now appears under the File Backup Sets tab on the Windows/Linux Servers page.

Create MS-SQL backup set for an instance

Backup set allows you to define the content to back up and the backup schedule for the server. Before creating a backup set, ensure that you have associated the instance with the administrative group. To create an MS-SQL backup set, perform the following steps:

Note: Phoenix displays the Assign Administrative Group page only if the server associated with the selected standalone instance is not mapped to any administrative group.

Step 1: Attach instance to an administrative group

An administrative group allows you to logically categorize your servers for better management. Before creating a backup set, you must first attach the instance to the administrative group.

To attach an instance to an existing administrative group

  1. Log on to Phoenix Management Console, select the organization from the menu bar at the top, and click Protect > MS-SQL Servers.
  2. Under the Instances/AGs tab on the MS-SQL Servers page, configure servers as follows:
    • For single-instance configuration: Select the instance and click Add New Backup Set. The Create SQL Backup Set: Assign Administrative Group wizard opens.
    • For multi-instances configuration: Select the instances and click Add New Backup Set. The Create SQL Backup Set: Assign Administrative Group wizard opens.
  3. From the Administrative Group drop-down list, select the required administrative group, and click Next: Create Backup Set. For more information about creating a backup set for the instance, see Create MS-SQL backup set.

 To attach SQL instance to a new administrative group

  1. Click Create New Group adjacent to the Administrative Group drop-down list.
  2. The Create New Administrative Group window opens.
  3. In the Name box, type the name of the administrative group.
  4. In the Description box, type a description for the administrative group.
  5. Click Save.
    The administrative group created now appears in the Administrative Group drop-down list on the Create SQL Backup Set: Assign Administrative Group wizard.
  6. From the Administrative Group drop-down list, select the new administrative group, and click Next: Create Backup Set.

Step 2: Create MS-SQL backup set for an instance

  1. Define backup content for MS-SQL instances as follows:
    1. Under the Storage & Backup Content tab, provide the following information:
      Field Description
      Storage The Phoenix storage where the backed up data of the MS-SQL server is stored.

      Select Content

       

      Exclude database(s): If you provide database names in the Exclude databases box, Phoenix excludes databases whose names are a partial or an exact match with the strings that you provided. The database names are case-sensitive. 
      If you have mirrored or encrypted databases, as well as databases with an apostrophe or a comma in their names, exclude these databases. 

      SQL_Storage_Backup_Content.PNG

      Note: Databases that are part of an AG are auto-excluded from the standalone instance backup.

  2. Under the Backup Policy tab, attach the backup policy to the instance. It is possible to create backup policies for File server and MS-SQL server with the same name. You can attach the instance to an existing backup policy or create a new backup policy.
  • Attach instance to an existing backup policy.
    1. From the Backup Policy drop-down list, select the required backup policy to attach it to the instance.
    2. Under the Policy Details section, verify the configuration summary of the selected backup policy, and click Finish. 
  • Attach instance to a new backup policy.
    1. Click Create New Backup Policy to define a new backup policy. The Create New Backup Policy: MS-SQL page opens.
      Perform the following steps:

Step 1: Provide backup policy summary details 

  1. Under the Summary tab, provide the following information:
    • Name: The name for the backup policy that you want to create.
    • Description: A short description of the backup policy. 
  2. Click Next to define the backup schedule.

Step 2: Define a backup schedule 

  1. Under the Backup Schedule tab, provide the following information:
    Field Description

    Backup Type

    Select Full backupDifferential backup, or Transaction Logs.  

    Start at

    The time when you want backups to start. In the adjacent box, select the AM or PM option depending on when you want backups to occur. 

    Duration (Hrs)

    The duration after which you want backup operations to stop. For example, if you set Start at to 5 AM and you set the duration to 5 hours, backups from your server start at 5 AM and stop at 10 AM, even if they do not complete. 

    Max Bandwidth (Mbps)

    The maximum bandwidth that each SQL server can consume while backing up data to Phoenix. For scheduled backup, the job will consume the assigned bandwidth. However, for manually triggered backup, the job will consume the available bandwidth on your network.

    Repeat on

    The days on which you want backups to occur.

    For transaction log backups, you can specify an interval of 5, 10, 15, 30, 45, 60, or 120 minutes. Log backups are triggered as soon as a full or differential backup completes. 

Note: Log backups are not applicable for databases in the simple recovery mode.

  1. Click Add More to create more schedules.

  2. To add multiple schedules, repeat step a as many times as the number of schedules that you want to create. To delete a schedule, click the delete icon next to the schedule. If you have only one schedule defined, you cannot delete it.

  3. By default, the Ignore backup duration for first backup option is enabled. When this option is enabled, it ignores the specified backup duration for the first backup job. The first backup job is complete when the first restore point is created. You can disable this option to enforce backup duration for the first backup job. 

  4. By default, the Automatic Retry check box is enabled. If you do not want to define the automatic retrial options, clear the Automatic Retry check box.
    Provide the following details for automatic retrial options:
    Field Description
    Max number of retries In an active schedule window, the maximum number of retry attempts for a job. By default, the field is set to 2 attempts.
    Wait interval before each retry The wait interval between each retry. By default, the field is set to 10 minutes.

    Automatic retry is not applicable for transaction log backups. For more details, see Backup retry.

Note: The snapshot timestamps for backup sets of the standalone instances are displayed according to the server time zone. For example, for servers located in New York and London, the timestamps are displayed according to EST and UTC time zones, respectively. 

  1. Click Next to define the retention details.

Step 3: Define retention 

  1. Under the Retention tab, provide the following information.
    Default_retention_policySQL.PNG
    Field Description
    All snapshots for The duration for which you want to retain all snapshots.
    Weekly revisions for The duration for which you want to retain weekly snapshots.
    Monthly revisions for The duration for which you want to retain monthly snapshots.
    Yearly revisions for The duration for which you want to retain yearly snapshots.

Note: Ensure that you enter a value in at least one of the fields. Phoenix treats the values in the empty fields as zero. 

  1. Click Finish to create the backup policy.
    The created backup policy is listed in the Backup Policy drop-down list. 

  2. From the Backup Policy list, select the created backup policy.
    Under the Policy Details section, verify the configuration summary of the new backup policy, and click Finish. 

The backup set created for the instance now appears under the SQL Backup Sets tab on the MS-SQL Servers page.

The agent backs up instance database based on the backup schedule and retains snapshots as defined in the retention period.

Create MS-SQL backup set for an availability group

Backup set allows you to define the content to back up and the backup schedule for the server. Before creating a backup set, ensure that you have associated the AG with the administrative group. To create an MS-SQL backup set, perform the following steps:

Note: Phoenix displays the Assign Administrative Group page only if the server associated with the selected AG is not mapped to any administrative group.

Step 1: Attach AG to an administrative group

An administrative group allows you to logically categorize your servers for better management. Before creating a backup set, you must first attach the AG to the administrative group.

To attach administrative group to an existing administrative group

  1. Log on to Phoenix Management Console, select the organization from the menu bar at the top, and click Protect > MS-SQL Servers.
  2. Under the Instances/AGs tab on the MS-SQL Servers page, configure servers as follows:
    • For single-AG configuration: Select the AG and click Add New Backup Set. The Create SQL Backup Set: Assign Administrative Group wizard opens.
    • For multi-AGs configuration: Select the AGs and click Add New Backup Set. The Create SQL Backup Set: Assign Administrative Group wizard opens.
  3. From the Administrative Group drop-down list, select the required administrative group, and click Next: Create Backup Set. For more information about creating a backup set for the server, see Create MS-SQL backup set.

To attach AG to a new administrative group

  1. Click Create New Group adjacent to the Administrative Group drop-down list.
  2. The Create New Administrative Group window opens.
  3. In the Name box, type the name of the administrative group.
  4. In the Description box, type a description for the administrative group.
  5. Click Save.
    The administrative group created now appears in the Administrative Group drop-down list on the Create SQL Backup Set: Assign Administrative Group wizard.
  6. From the Administrative Group drop-down list, select the new administrative group, and click Next: Create Backup Set.

Step 2: Create MS-SQL backup set for AG

  1. Define backup content for MS-SQL AGs as follows:
    1. Under the Storage & Backup Content tab, provide the following information:
      Field Description
      Storage The Phoenix storage where the backed up data of the MS-SQL server is stored.
      Time Zone

      The time zone of the primary server of the availability group in which Phoenix triggers the backups. 

      Note : Phoenix displays the Time Zone field only if you are configuring backup set for AG.

      Select Content

       

      Exclude database(s): If you provide database names in the Exclude databases box, Phoenix excludes databases whose names are a partial or an exact match with the strings that you provided. The database names are case-sensitive. 
      If you have mirrored or encrypted databases, as well as databases with an apostrophe or a comma in their names, exclude these databases. 

      Note: Databases that are part of an AG are auto-excluded from the standalone instance backup.

  2. Under the Backup Policy tab, attach the backup policy to the AG. It is possible to create backup policies for File server and MS-SQL server with the same name. You can attach the AG to an existing backup policy or create a new backup policy.
  • Attach AG to an existing backup policy.
    1. From the Backup Policy drop-down list, select the required backup policy to attach it to the AG.
    2. Under the Policy Details section, verify the configuration summary of the selected backup policy, and click Finish. 
  • Attach AG to a new backup policy.
    1. Click Create New Backup Policy to define a new backup policy. The Create New Backup Policy: MS-SQL page opens.
      Perform the following steps:

Step 1: Provide backup policy summary details 

  1. Under the Summary tab, provide the following information:
    • Name: The name for the backup policy that you want to create.
    • Description: A short description of the backup policy. 
  2. Click Next to define the backup schedule.

Step 2: Define a backup schedule 

  1. Under the Backup Schedule tab, provide the following information:
    Field Description

    Backup Type

    Select Full backupDifferential backup, or Transaction Logs.  

    Start at

    The time when you want backups to start. In the adjacent box, select the AM or PM option depending on when you want backups to occur. 

    Duration (Hrs)

    The duration after which you want backup operations to stop. For example, if you set Start at to 5 AM and you set the duration to 5 hours, backups from your server start at 5 AM and stop at 10 AM, even if they do not complete. 

    Max Bandwidth (Mbps)

    The maximum bandwidth that each SQL server can consume while backing up data to Phoenix. For scheduled backup, the job will consume the assigned bandwidth. However, for manually triggered backup, the job will consume the available bandwidth on your network.

    Repeat on

    The days on which you want backups to occur.

    For transaction log backups, you can specify an interval of 5, 10, 15, 30, 45, 60, or 120 minutes. Log backups are triggered as soon as a full or differential backup completes. 

Note: Log backups are not applicable for databases in the simple recovery mode.

  1. Click Add More to create more schedules.

  2. To add multiple schedules, repeat step a as many times as the number of schedules that you want to create. To delete a schedule, click the delete icon next to the schedule. If you have only one schedule defined, you cannot delete it.

  3. By default, the Ignore backup duration for first backup option is enabled. When this option is enabled, it ignores the specified backup duration for the first backup job. The first backup job is complete when the first restore point is created. You can disable this option to enforce backup duration for the first backup job. 

  4. By default, the Automatic Retry check box is enabled. If you do not want to define the automatic retrial options, clear the Automatic Retry check box.
    Provide the following details for automatic retrial options:
    Field Description
    Max number of retries In an active schedule window, the maximum number of retry attempts for a job. By default, the field is set to 2 attempts.
    Wait interval before each retry The wait interval between each retry. By default, the field is set to 10 minutes.

    Automatic retry is not applicable for transaction log backups. For more details, see Backup retry.

Note: The snapshot timestamps for backup sets of the AGs are displayed according to the time zone configured during creation of backup set.

  1. Click Next to define the retention details.

Step 3: Define retention 

  1. Under the Retention tab, provide the following information.
    Field Description
    All snapshots for The duration for which you want to retain all snapshots.
    Weekly revisions for The duration for which you want to retain weekly snapshots.
    Monthly revisions for The duration for which you want to retain monthly snapshots.
    Yearly revisions for The duration for which you want to retain yearly snapshots.

Note: Ensure that you enter a value in at least one of the fields. Phoenix treats the values in the empty fields as zero. 

  1. Click Finish to create the backup policy.
    The created backup policy is listed in the Backup Policy drop-down list. 

  2. From the Backup Policy list, select the created backup policy.
    Under the Policy Details section, verify the configuration summary of the new backup policy, and click Finish. 

The backup set created for the AG now appears under the SQL Backup Sets tab on the MS-SQL Servers page.

The agent backs up data from the AG based on the backup schedule and retains snapshots as defined in the retention period based on the time zone defined in step a

Next step

If you have deployed CloudCache, you can attach backup sets to the CloudCache. For more information, see Attach a new backup set to CloudCache.