Skip to main content

 

Druva Documentation

Manage backup policies

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

Overview

Backup policies are rules that define the type of data for backup and the schedule for automatic backups. You can create a backup policy and attach it to one or more server groups. After you assign the servers to server groups, data from these servers is backed up according to the backup policy. Because backup policies are assigned to servers groups and not individual servers, management of data backups across multiple servers is simplified.

Note: Phoenix creates a default backup policy for your setup. The default backup policy is configured to back up all file types. You can assign the default backup policy to one or more server groups.You can also update or delete this backup policy.

Best practices for creating a backup policy

To account for the difference in the SQL server and file server architecture, Phoenix requires the creation of separate backup policies for file servers and SQL servers. Because Phoenix allows assigning only one backup policy to a server group, assigning a backup policy to a server group implies that the server group can include file servers or SQL servers, but not both. 

You can create as many backup policies as you want, depending on the number of servers and the frequency of data change on these servers. For example, for file servers that change frequently, you can create a backup policy, and define a schedule for a weekly backup for longer duration, along with short-burst backups every second day.

In a production environment, we recommend that you create platform-specific backup policies. Additionally, if you expect Phoenix to back up different types of data from different versions of Windows and Linux servers, create a separate backup policy for each version of Windows and Linux servers respectively. 

The backup policy defines the backup schedules for your file servers. The schedules that you set depends on the volume and frequency of data change on your file servers. The schedules also depend on the availability of bandwidth for data transmission to Phoenix cloud. If you expect a large dataset during backups, you can schedule backups to run during off-peak hours (such as weekends or after a workday). 

Note: The backup schedule that you define in a backup policy depends on your organization's policies. 

Example backup policy

As an example, consider two remote offices, A and B, both having 5 SQL servers and file servers each. The remote office location A has Windows file servers that see large data changes, mostly to the image files that reside on these servers. Most of the times, data changes include new additions. The file servers in remote office location B run on the Linux operating system and also change frequently. These servers contain mostly text files. However, the changes are minor and are generally updates. For file servers of the remote location A, consider creating a backup policy for Windows servers and configuring it to include all types of image files. For this backup policy, you can schedule backups to run for longer durations twice in a week during off-peak hours. You can also include daily short-burst backups at the end of a workday. Similarly, for file servers at remote location B, you can create a backup policy that includes all text files. Set schedules for this policy such that a backup runs once in a week for longer duration during off-peak hours, along with short-burst backups every second day. 

Note: This is just an example scenario. The backup policy configuration for your setup depend on your server data needs and your organization's policies. However, you can request for backup policy recommendations by writing to the Druva Support team (support@druva.com). 

Add a backup policy

This topic provides instructions to create a backup policy for file servers.

Before you begin

Before adding a backup policy for file servers, ensure you have read:

To add a backup policy

Step 1: Provide general information

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies.
  4. Click Add Backup Policy.
  5. On the Add Backup Policy page, provide the following details:
    Field Description
    Name The name for this backup policy. 
    Description  A short description of this backup policy.
    Policy Type Select File server. 
  6. Click Next

Step 2: Select folders for backup and include or exclude files from selected folders

  1. On the Backup Content page,  provide the following details:
    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,  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 Add option. 

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

    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

    Select 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

  2. Click Next
     

Step 3: Specify backup schedule and its behavior

  1.  On the Backup Schedule, provide the following details.
    Field Description

    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. 

    Note: Backup operations follow the time zone of the servers. For example, if you set a schedule for backups to start at 6 AM backups from servers located in New York and London will start at 6 AM EST and 6 AM UTC, respectively. 

    Duration      

    The duration after which you want backup operations to stop.

    For example, if you set Start at to 9 AM and you set the duration to 2 hours, backups from your server start at 9 AM and stop at 11 AM, even if they do not complete.

    Max Bandwidth (Mbps)

    The maximum bandwidth that each 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.
    Delete a schedule The delete icon only appears if you have added more than one schedules defined. If you have only one schedule defined, you cannot delete it.
    Add More  To create multiple schedules, click Add More as many times as the number of schedules that you want to create.

    Ignore backup duration for first backup

    Ignores 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 checkbox.

    Max number of retries

    In an active schedule window, the maximum number of retry attempts for a job.

    Note: By default, the field is set to 2 attempts.

    Wait interval before each retry

    The wait interval between each retry.

    Note: 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.

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.

Step 4: Specify settings for pre-backup and post-backup scripts

  1. On the Pre/Post Scripts settings, provide the following details:

    Field

    Description

    Enable scripts for Windows servers  

    Select the check box to enable the execution of pre and post backup scripts on Windows server. When you select the checkbox, 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 checkbox to enable the execution of pre and post backup scripts on Linux server. When you select the checkbox, 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

    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 execution if it does not complete in XX Minutes

    Select the time in minutes after which the backup script execution to abort.

  2. Click Finish to confirm the schedule.

Copy a file server backup policy

To create multiple copies of a backup policy without having to create a backup policy each time, you can create a copy of an existing backup policy.

When you create a copy of a backup policy, the newly-created backup policy is identical to the policy that it was copied from. You can modify the properties of this backup policy according to your requirements.

To copy a file server backup policy

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies.
  4. Select a backup policy, and click Copy.
  5. On the Copy Backup Policy page, provide the following details:
  • New backup policy name: The name for the new backup policy.
  • Description: A short description for the profile.

Note: The Selected backup policy field displays the name of the backup policy that you selected to copy . 

  1. Click Copy

Update backup content of a backup policy

If you are a cloud administrator or a group administrator, you can update the backup content of existing backup policies.

While updating the backup content of a backup policy, you can specify folders for backup. Additionally, you can also include or exclude file types from backup. 

To update selected folders

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies
  4. Click the backup policy that you want to update.
  5. Under the Content area, click Edit.
  6. To back up all folders, select All folders.
    To back up a specific folder, click Specific folders, type the absolute path to the folder in the Specify subfolder path box, and then click Add. 
  7. To exclude a subfolder, type the relative or absolute path to the subfolder in the Enter subfolder path to add box under Exclude subfolders, and then click Add
Note: For Linux servers, exclude cgroups from backup.

Update file inclusion or exclusion

  1. If you want to exclude some files, click Exclude file types.
  2. Click in the box below, and select the file types that you want to exclude from the backup. 

Note: If you do not see your file type, click More file extensions to exclude, and in the box, type the file extensions that you want to exclude from backup. Type an extension preceded by an asterisk (*), for example, *.dotm. Separate consecutive entires using a comma. 

  1. If you want to back up specific files, click Include file types.
  2. Click in the box below, and select the file types that you want to include for backup.

Note: If you do not see your file type, click More file extensions to include, and in the box, type the file extensions that you want to include for backup. Type an extension preceded by an asterisk (*), for example, *.dotm. Separate consecutive entries using a comma.

  1. Click Update Backup Policy.

Update backup policy schedule

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies
  4. Click the backup policy for which you want to update the schedule.
  5. Under the Schedule section, click Edit.
  6. On the Edit Backup Policy Schedule page, update the following:
    Field Description

    Start at

    The time when you want backups to start.

    Duration      

     

    The duration after which you want backup operations to stop.

    For example, if you set Start at to 9 AM and you set the duration to 2 hours, backups from your server start at 9 AM and stop at 11 AM, even if they do not complete.

    Max Bandwidth (Mbps)

     

    The maximum bandwidth that each 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 repeat.
    Delete a schedule The delete icon only appears if you have added more than one schedules defined. If you have only one schedule defined, you cannot delete it.

    Add More

    To create multiple schedules, click Add More as many times as the number of schedules that you want to create.

    Ignore backup duration for first backup

     

    Ignores 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

     

    Enables Phoenix to automatically retry failed backup attempts. Automatic backup retries will occur only between the defined scheduled duration.

    For more information, see  Backup Retry.

    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.

    Note: 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.
    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

    See also, File Server FAQs.

  7. Click Save.

Update pre-backup and post-backup script settings

If you are a cloud administrator or a group administrator, you can update the pre-backup and post-backup script settings of the existing backup policies.

While updating the backup script settings of a backup policy, you can specify the location of pre and post backup scripts for execution for Windows and Linux servers. Additionally, you can also configure the setting to skip a backup, if the backup pre-script is unavailable at the specified location.

Procedure

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies
  4. On the Manage Backup Policies page, click the backup policy that you want to update.
  5. Under the Pre/Post Backup Script area, click Edit.
  6. On the Edit Backup Policy Pre/Post Script page, update the following settings:

    Field

    Description

    Enable scripts for Windows servers  

    Select this checkbox to enable the execution of pre and post backup scripts on Windows server. When you select the checkbox, 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 checkbox to enable the execution of pre and post backup scripts on Linux server. When you select the checkbox, the Specify scripts location field gets enabled.

    Specify scripts location

    In the Specify scripts location field, specify the folder path 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 execution if it does not complete in XX Minutes

    Select the time in minutes after which the backup script execution to abort.

  7. Click Save to save the changes made.

View associated server groups

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies.
  4. Click the File server backup policy for which you want to view the associated server groups.
  5. In the Server Groups panel, you can view the list of associated server groups.

Remove a backup policy

If you are a cloud administrator, you can remove backup policies that are not assigned to server groups.

Procedure

  1. Log on to Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies
  4. Click the backup policy that you want to remove.
  5. Click Remove Backup Policy.

Note: You cannot delete backup policies that you have assigned to server groups. 

  • Was this article helpful?