SnapCenter Software 5 Manuals ( CA08871-403 )
Create backup policies for Exchange Server databases
You can create a backup policy for the Exchange resources or for the resource groups before you use SnapCenter to back up Microsoft Exchange Server resources, or you can create a backup policy at the time you create a resource group or back up a single resource.
-
You must have defined your data protection strategy.
For details, see the information about defining a data protection strategy for Exchange databases.
-
You must have prepared for data protection by completing tasks such as installing SnapCenter, adding hosts, identifying resources, and creating storage system connections.
-
You must have refreshed (discovered) the Exchange Server resources.
-
If you are replicating Snapshot copies to a mirror or vault, the SnapCenter administrator must have assigned the storage virtual machines (SVMs) for both the source volumes and destination volumes to you.
-
If you want to run the PowerShell scripts in prescripts and postscripts, you should set the value of the
usePowershellProcessforScriptsparameter to true in theweb.configfile.The default value is false
-
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.
-
The SCRIPTS_PATH is defined using the PredefinedWindowsScriptsDirectory key located in the SMCoreServiceHost.exe.Config file of the plug-in host.
If needed, you can change this path and restart SMcore service. It is recommended that you use the default path for security.
The value of the key can be displayed from swagger through the API: API /4.7/configsettings
You can use the GET API to display the value of the key. SET API is not supported.
Best Practice: It’s best 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.
-
SnapLock
-
If 'Retain the backup copies for a specific number of days' option is selected, then the SnapLock retention period must be lesser than or equal to the mentioned retention days.
Specifying a Snapshot copy locking period prevents deletion of the Snapshot copies until the retention period expires. This could lead to retaining a larger number of Snapshot copies than the count specified in the policy.
For ONTAP 9.12.1 and below version, if you specify a Snapshot copy locking period, the clones created from the tamper proof Snapshot copies will inherit the SnapLock expiry time. You should manually cleanup the clones post the SnapLock expiry time.
Primary SnapLock settings are managed in SnapCenter backup policy and the secondary SnapLock settings are managed by ONTAP.
-
-
In the left navigation pane, click Settings.
-
In the Settings page, click Policies.
-
Click New.
-
In the Name page, enter the policy name and description.
-
In the Backup Type page, perform the following steps:
-
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.
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. This directory contains the pointer to the incremental changes for the Exchange database and it is not equivalent to the complete log files.
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.
You should define the space required for log backups based on the full backup retention and not based on Up-to-the-minute (UTM) retention. Create separate vault policies for logs and databases when dealing with Exchange volumes (LUNs), and set the keep (retention) for the log policy to twice the number for each label as the database policy, using the same labels. -
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 database availability groups (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.
In cluster configurations, the backups are retained at each node of the cluster according to the retention settings set in the policy. If the owner node of the cluster changes, the backups of the previous owner node will be retained. The retention is applicable only at the node level. -
In the Schedule frequency section, select one or more of the frequency types: On demand, Hourly, Daily, Weekly, and Monthly.
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. If you have scheduled for 2:00 a.m., the schedule will not be triggered during daylight saving time (DST).
-
-
In the Retention page, configure the retention settings.
The options displayed depend upon the backup type and frequency type you previously selected.
The maximum retention value is 1018 for resources on ONTAP 9.7 or later. Backups will fail if retention is set to a value higher than what the underlying ONTAP version supports. You must set the retention count to 2 or higher if you plan to enable SnapVault replication. If you set the retention count to 1, the retention operation might fail because the first Snapshot copy is the reference Snapshot copy for the SnapVault relationship until a newer Snapshot copy is replicated to the target. -
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 Number of full backups for which logs are retained, and specify the number of full backups for which you want up-to-the-minute restorability.
Up-to-the-minute (UTM) retention applies to log backup created via full or log backup. For example, if UTM retention settings is configured to retain log backups of the last 5 full backups, then the log backups of the last 5 full backups are retained.
The log folders created as part of full and log backups are automatically deleted as part of UTM. You cannot delete the log folders manually. For example, if the retention setting of full or full and log backup is set for 1 month and UTM retention is set to 10 Days, then the log folder created as part of these backups will be deleted as per UTM. As a result, only 10 days log folders will be there and all other backups are marked for point-in-time restore.
You can set UTM retention value as 0, if you do not want to perform up-to-the-minute restore. This will enable point-in-time restore operation.
Best Practice: It’s best that the setting must be equal to the setting for Total Snapshot copies (full backups) in the Full 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.
Snapshot copy locking period
Select Snapshot copy locking period, and select days, months, or years.
SnapLock retention period should be less than 100 years.
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.
-
In the Full backup retention settings section, select one of the following for on-demand backups, and then 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).
Snapshot copy locking period
Select Snapshot copy locking period, and select days, months, or years.
SnapLock retention period should be less than 100 years.
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\Fujitsu\SnapCenter WebApp\web.config file.
<add key="MaxLogBackupOnlyCountWithoutFullBackup" value="10">
In the example, the value 10 means you keep up to 10 log backups on the host.
-
-
-
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
During secondary replication, the SnapLock expiry time loads the primary SnapLock expiry time.
Clicking the Refresh button in the Topology page refreshes the secondary and primary SnapLock expiry time that are retrieved from ONTAP.
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
Select a Snapshot label.
Depending on the Snapshot copy label that you select, ONTAP applies the secondary Snapshot copy retention policy that matches the label.
If you have selected Update SnapMirror after creating a local Snapshot copy, you can optionally specify the secondary policy label. However, if you have selected Update SnapVault after creating a local Snapshot copy, you should specify the secondary policy label. Error retry count
Enter the number of replication attempts that should occur before the process halts.
You should configure SnapMirror retention policy in ONTAP for the secondary storage to avoid reaching the maximum limit of Snapshot copies on the secondary storage. -
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.
The prescripts or postscripts path should not include drives or shares. The path should be relative to the SCRIPTS_PATH.
-
-
Review the summary, and then click Finish.
