Creating backup policies for Exchange Server databases

You can create a backup policy for Exchange resources or for the resource groups before you use SnapCenter to back up Exchange Server resources, or you can create a backup policy at the time you create a resource group or back up a single resource.

Before you begin

About this task

A backup policy is a set of rules that governs how you manage and retain backups, and how frequently the resource or resource group is backed up. Additionally, you can specify script settings. Specifying options in a policy saves time when you want to reuse the policy for another resource group.

Full backup retention is specific to a given policy. A database or resource using policy A with a full backup retention of 4 retains 4 full backups and has no effect on policy B for the same database or resource, which might have a retention of 3 to retain 3 full backups.

Log backup retention is effective across policies and applies to all log backups for a database or resource. Therefore, when a full backup is performed using policy B, the log retention setting affects log backups created by policy A on the same database or resource. Similarly, the log retention setting for policy A affects log backups created by policy B on the same database.

Best Practice: NetApp recommends that you configure the secondary retention policy based on the number of full and log backups, overall, that you want to retain. When you configure secondary retention policies, keep in mind that when databases and logs that are in different volumes, each backup can have three Snapshot copies, and when databases and logs are in the same volume, each backup can have two Snapshot copies.

Most of the fields on these wizard pages are self-explanatory. The following information describes some of the fields for which you might require guidance.

Steps

  1. In the left navigation pane, click Settings.
  2. In the Settings page, click Policies.
  3. Click New.
  4. In the Name page, enter the policy name and description.
  5. In the Backup Type page, perform the following steps:
    1. Choose backup type:
      If you want to... Do this...
      Back up the database files and the required transaction logs Select Full backup and Log backup.

      Databases are backed up with log truncation, and all logs are backed up, including the truncated logs.

      Note: This is the recommended backup type.
      Back up the database files and the uncommitted transaction logs Select Full backup.

      Databases are backed up with log truncation, and truncated logs are not backed up.

      Back up all the transaction logs Select Log backup.

      All transaction logs on the active file system are backed up, and there is no log truncation. A SceBackupInfo directory is created on the same disk as the live log.

      Back up all database files and transaction logs without truncating the transaction log files Select Copy Backup.

      All databases and all logs are backed up, and there is no log truncation. You typically use this backup type for reseeding a replica or for testing or diagnosing a problem.

    2. In the Database Availability Group Settings section, select an action:
      For this field… Do this…
      Back up active copies Select this option to back up only the active copies of the selected database.

      For DAGs, this option backs up only active copies of all databases in the DAG.

      Passive copies are not backed up.

      Back up copies on servers to be selected at backup job creation time Select this option to back up any copies of the databases on the selected servers, both active and passive.

      For DAGs, this option backs up both active and passive copies of all databases on the selected servers.

    3. In the Schedule frequency section, select one or more of the frequency types: Hourly, Daily, Weekly, and Monthly.
      Note: You can specify the schedule (start date, end date) for backup operations while creating a resource group. This enables you to create resource groups that share the same policy and backup frequency, but lets you assign different backup schedules to each policy.
  6. In the Retention page, configure the retention settings.
    The options displayed depend upon the backup type and frequency type you previously selected.
    Note: The maximum retention value is 1018 for resources on ONTAP 9.4 or later, and 254 for resources on ONTAP 9.3 or earlier. Backups will fail if retention is set to a value higher than what the underlying ONTAP version supports.
    1. In the Log backups retention settings section, select one of the following:
      If you want to… Do this…
      Retain only a specific number of log backups Select the Number of full backups for which logs are retained option, and specify the number of full backups for which you want up-to-the-minute restorability.

      For up-to-the-minute (UTM) restore operations, the retention setting is the number of full backups for which the log backups are retained. If you configure UTM retention (the number of full backups for which logs are retained) to 5, the log backups up to the most recent 5 full backups for this database are retained, and the rest are deleted.

      Note: The setting must be equal to the setting for Total Snapshot copies (full backups) in theFull backup retention settings section. This ensures that log files are retained for each full backup.
      Retain the backup copies for a specific number of days Select the Keep log backups for last option, and specify the number of days to keep the log backup copies.

      The log backups up to the number of days of full backups are retained.

      If you selected Log backup as the backup type, log backups are retained as part of the up-to-the-minute retention settings for full backups.

    2. In the Full backup retention settings section, select one of the following for on-demand backups and select one for full backups:
      For this field... Do this...
      Retain only a specific number of Snapshot copies If you want to specify the number of full backups to keep, select the Total Snapshot copies to keep option, and specify the number of Snapshot copies (full backups) to retain.

      If the number of full backups exceeds the specified number, the full backups that exceed the specified number are deleted, with the oldest copies deleted first.

      Retain full backups for a specific number of days Select the Keep Snapshot copies for option, and specify the number of days to keep Snapshot copies (full backups).
      Note: If you have a database with only log backups and no full backups on a host in a DAG configuration, the log backups are retained in the following ways:
      • By default, SnapCenter finds the oldest full backup for this database in all the other hosts in the DAG, and deletes all log backups on this host that were taken before the full backup.
      • You can override the above default retention behavior for a database on a host in a DAG with only log backups by adding the key "MaxLogBackupOnlyCountWithoutFullBackup" in the C:\Program Files\NetApp\SnapCenter WebApp\web.config file. For example, <add key="MaxLogBackupOnlyCountWithoutFullBackup" value="10">

        In the example, the value 10 means you keep up to 10 log backups on the host.

  7. In the Replication page, select one or both of the following secondary replication options:
    For this field... Do this...
    Update SnapMirror after creating a local Snapshot copy Select this option to keep mirror copies of backup sets on another volume (SnapMirror).
    Update SnapVault after creating a local Snapshot copy Select this option to perform disk-to-disk backup replication.
    Secondary policy label Depending on the Snapshot copy label that you select, ONTAP applies the secondary Snapshot copy retention policy that matches the label.
    Error retry count Enter the number of replication attempts that should occur before the process halts.
  8. Optional: In the Script page, enter the path and the arguments of the prescript or postscript that should be run before or after the backup operation, respectively.

    Prescript backup arguments include "$Database" and "$ServerInstance".

    Postscript backup arguments include $Database, $ServerInstance, $BackupName, $LogDirectory, and $LogSnapshot.

    You can run a script to update SNMP traps, automate alerts, send logs, and so on.

  9. Review the summary, and then click Finish.