SnapManager backup options

Use the Backup Settings dialog box to configure default settings for SnapManager backup operations.

Configuring the profile of a full database backup

To configure the profile of a full database backup, complete the following steps.

Note: For a complete list of parameters that are applied to a full database backup operation, see "Information you need to specify for a full database backup" in Backing up, replicating, and archiving databases using SnapManager.

Step	Action
1	Open the Backup Settings dialog box using any of the following methods: From the Actions pane, select Backup Settings. From the Action menu, click Backup Settings. From the Backup Wizard, go to the Backup Options screen and click Backup Settings. Result The Backup Settings dialog box appears. The Full Database Backup option is active by default and displays the current settings.
2	In the "Select a backup naming convention..." panel, specify the naming convention you want used to form database backup Snapshot copy names and SnapInfo directory Snapshot copy names. If you want the most recent backup to be identified by the Snapshot copy name that includes the string recent, select the "Use Generic..." option. If you want all Snapshot copy names, even for the most recent backup, to contain the Snapshot copy creation date and time, select the "Use Unique Naming convention" option. This option is selected by default. For more detailed information, see "SnapManager backup set naming conventions" in How SnapManager backup data is organized.
3	In the "Verify mounted online databases" panel, select whether you want to run verification against the live database before the backup, after the backup, or both before and after the backup. If you want to run the DBCC utility against the live database before the database is backed up, select the "Run DBCC physical integrity verification before the backup" option. If you want to run the DBCC utility against the live database after the database is backed up, select the "Run DBCC physical integrity verification after the backup" option. Note: By default, both options are not selected because database verification is a time-consuming activity.
4	To apply your changes and close the dialog box, click OK. Result The new settings will be applied to all subsequent full database backups.

Configuring the profile of a transaction log backup

To configure the profile of a transaction log backup, complete the following steps.

Note: For a complete list of parameters that are applied to a transaction log backup operation, see "Information you need to specify when creating a transaction log backup" in Managing transaction log backups using SnapManager.

Step	Action
1	Open the Backup Settings dialog box using any of the following methods: From the Actions pane, select Backup Settings. From the Action menu, click Backup Settings. From the Backup Wizard, go to the Backup Options screen and click Backup Settings. Result The Backup Settings dialog box appears. The Full Database Backup option is active by default and displays the current settings.
2	In the dialog box, click the "Transaction Log Backup" tab. Result The Transaction Log Backup tab displays the current settings.
3	In the "Transaction Log Backup" tab, select "Create Snapshot of the SnapInfo drive after backup" to create a Snapshot copy of the snapInfo directory after the backup operation finishes.
4	Select "Delete SnapInfo Snapshots" to delete SnapInfo Snapshot copies based on their number or the number of retention days.
5	If you want to run the DBCC utility against the live database after the database is backed up, select the "Truncate committed transactions in the transaction log" option.
6	If you want some or all of the transaction logs copied to the repository share, select "Copy transaction log backups to share. Determine if this applies to all databases, or only to Availability Group databases, and then set the retention policy.
7	To apply your changes and close the dialog box, click OK. Result The new settings are applied to all subsequent full database backups.

Configuring backup concurrency

Microsoft recommends a maximum of 35 databases per backup Snapshot copy when running out of SQL Server thread resources.

To set the maximum number of databases per Snapshot copy, enter a number in the field.

Note: During backup, SnapManager might use a different number of maximum databases per Snapshot copy than what is configured in the Backup Settings dialog box. This happens because SnapManager tries to use the smallest number of Snapshot copies as possible. For example, if the maximum databases per Snapshot copy setting is 35 and there are 45 databases to backup, SnapManager might back up all 45 databases in the same Snapshot copy operation.