Backing up, replicating, and archiving databases using SnapManager

SnapManager provides two ways for you to start or schedule a full database backup: using the Backup wizard or using the Backup and Verify option.

Information you need to specify for a full database backup

A full database backup operation is specified using a combination of parameters.

Job-specific parameters

Each time you start or schedule a full database backup, you must specify the following information in either the Backup and Verification window or in the Backup wizard.

The databases you want to back up
You can back up databases from the same host or remote hosts, including different SQL instances on the same host. You can configure these options in the "Backup and Verify" window using the "Federated Backup" option.
When you select one database, SnapManager automatically selects all other databases that are located on the same Data ONTAP storage volume. SnapManager enables you to clear automatically selected databases. For example:
- You can clear databases that reside on a different LUN from the databases you selected, even if the LUN is on the same storage volume. If the other LUN stores only a single database, you can clear or re-select that database individually. If the other LUN houses multiple databases, you must clear or re-select those databases as a group.
- In the case of a stream-based full database backup, you can clear any automatically selected database. However, unless the selected databases share the same storage with other databases, SnapManager asks you to confirm your selection; backing up only a subset of the databases that reside on the same volume is not recommended. For more information about the stream-based and online Snapshot backup methods, see later in this topic.
When you select databases at the SQL Server instance level and one of the selected databases cannot be backed up for an unexpected reason (such as the database being offline or in a loading state at the time of the backup), the full database backup operation progresses as follows:
- The backup report includes a message at the beginning of the summary section that indicates that the backup was only partially completed because one or more databases were skipped.
- A warning event is logged to the event log. The description field of this event contains the summary section of the report.
- If e-mail notification is enabled, an email notification is sent to the configured email address.
  
  If the databases are moved to the local disk later, the scheduled backup operation skips backup deletion.
  
  Note: For an instance-level transaction-log-only backup operation in which one of the selected databases cannot be backed up, the operation proceeds in the same manner as described above.
Database has the full-text search option enabled, the full-text search catalogs are visible when you click the "+" next to the database name. The full text catalogs can be migrated, backed up, and restored along with the other files or file groups of the database.
Which backup management group you want to assign to this backup
For details, see Using backup management groups in backup and verification.
The operation asks whether you want to automatically run a transaction log backup after the full database backup finishes.
The operation asks whether you want to automatically delete the oldest full database backups within this backup management group (recommended to manage the number of Snapshot copies)
For a description of this option, see "Automatic deletion of the oldest backups in a management group" in Ways to manage the number of backup sets kept online.
If you select to automatically delete the oldest full database backups within this backup management group: the operation asks whether you also want to retain up-to-the-minute restore ability for all backups.
For a description of this option, see "Option to retain up-to-the-minute restore ability" in Ways to manage the number of backup sets kept online.
The operation asks whether you want to perform a database integrity verification of the backup set after the full database backup is complete
You can back up an Availability Group from one or multiple replicas. You configure this in the Backup and Verify window using Availability Group Backup option.
Use the Availability Group backup option to perform Availability Group level database backups. To do this, make the backup target the Availability Group, instead of databases. When a backup is on the Availability Group level, further backup policies can be specified, and the backup can happen potentially on any replica of the Availability Group when the backup is scheduled.

Note: Although it is possible to restore from an unverified backup, you should restore only from verified backups.

The operation asks whether you want to run a command after the backup is complete (usually done to archive backups)
The operation asks if the volumes you are backing up to are SnapMirror sources: whether you want the destination volumes to be updated after the full database backup is complete.
For more information about this option, see Replicating backups to mirrored volumes.
The operation asks whether you want to run the backup now or schedule it for later

Note: If you want to schedule the backup to run later, you also need to know the job scheduling information.

Backup settings The following list summarizes the backup settings that pertain to full database backups:

The operation asks whether you want the backup set to be named using generic ("__recent") or unique (time-stamped) naming conventions
For more information, see "SnapManager backup set naming conventions in "How SnapManager backup data is organized.
The operation asks whether you want to verify the integrity of the live database before the backup is performed and whether you want to verify the integrity of the live database after the backup is performed

Note: Verifying the integrity of the live database is a time-consuming operation. By default, neither of these options is selected.

The preceding options are configured using the Full Database Backup option of the SnapManager for SQL Server-Backup dialog box, described in "Configuring the profile of a full database backup" in SnapManager backup options.

The SnapManager for SQL Server-Backup dialog box can be accessed from the Backup and Verify option, as well as from the Backup wizard.

If you are using the Backup and Verify option, you can open the SnapManager for SQL Server-Backup dialog box from the Actions pane.
From within the Backup wizard, you can open the Backup Settings dialog box by clicking the Backup Settings button in the Advanced Backup Options screen.

Verification settings: The following list summarizes the settings that pertain to database verification:

The operation asks which SQL Server is used to perform database verification
This is configured using the SQL Server option of the Verification Settings dialog box, described in "Selecting the database verification server" in Database integrity verification options. If you will be specifying a remote verification server, be sure it is set up properly, as described in "Requirements for a remote verification server" in Database integrity verification options.

Note: Be careful not to schedule backups while verification is in progress. Doing so can create a "busy Snapshot" which might cause problems when you attempt to delete some Snapshot copies.

The following precautions will help you to avoid creating a busy Snapshot situation:
- Do not schedule backups while a verification is in progress.
- Do not create backup sets at the volume level or the SnapDrive level.
For information about busy Snapshot copies, see "Busy Snapshot error prevents deletion of backup set" in Explicitly deleting backup sets using SnapManager.
The operation asks which DBCC options are used to verify database backup sets
This is configured using the DBCC Options option of the Verification Settings dialog box, described in "Selecting DBCC options" in Database integrity verification options.

The Verification Settings dialog box can be accessed from the Backup and Verify option, as well as from the Backup wizard:

If you are using the Backup and Verify option, select "Verify most recent unverified Snapshot backups only" to open the Verification Settings tab.
At least two of the most recent SnapManager Snapshot copies that were used for SnapVault updates need to be kept online on the primary storage system.
You can use SnapManager to delete backup sets outside the backup process. When SnapVault is used, keep at least two of the most recent Snapshot copies used for the SnapVault updates until SnapVault updates for a given backup are complete. To check which Snapshot copies are required for the SnapVault relationships, use the SnapVault destinations -s command on the SnapVault primary storage system.
When you use SnapManager to automatically delete older backup sets as part of a backup process, be sure to configure the "Delete backups In excess of" option to a number that is equal to or greater than two. If backups are automatically deleted based on time rather than quantity using the "Delete backups Older than" option, be sure to specify a number of days that will allow at least two of the Snapshot copies used for the SnapVault updates to remain online. This information also applies to deleting backups using the Delete Backup option from the SnapManager Action pane.

Note: This applies only to Snapshot copies that are used for SnapVault updates.

The SnapVault option is not available for VMDKs.
From within the Backup wizard, you can open the Verification Settings dialog box by clicking "Verification Settings" button in the Verification Settings screen.

Note: The Verification Settings screen appears only if you are specifying a "Full database backup" or a "Verify most recent backup set backups" operation; the SnapManager Backup wizard does not present this screen if you are specifying a "Transaction log backup only" operation.

Full database backup using Backup and Verify

To start or schedule a full database backup using Backup and Verify, complete the following steps.

With a full database backup you can choose to also back up the associated transaction logs after the database backup is complete. If you want to back up only transaction logs, see Managing transaction log backups using SnapManager.

You can run only one full database backup at a time. However, you can start a full database backup when a deferred verification is already running.

Note: For a list of information you need to provide as you complete these steps, see the section "Information you need to specify for a full database backup" which appears earlier in this topic.

Step	Action
1	In the SnapManager console root, double-click the server you want to use.
2	Select the Backup option in the Scope pane.
3	In the Results pane, select the databases for which you want to perform a full backup. When you select a database, SnapManager automatically selects all other databases that reside on the same storage system and storage system volume. When you select a database that resides on a VMDK, SnapManager automatically selects all the databases that reside on the VMDKs. For information about clearing any automatically selected databases, see the bullet "Which databases you want to backup" under "Job-specific parameters". Note: When SnapManager is running on VMDKs, you cannot select a physical SQL Server as the verification server. When you select databases at the SQL Server instance level, SnapManager reports any offline databases as skipped in the backup report. For more information, see "Information you need to specify for a full database backup" in Managing transaction log backups using SnapManager.
4	In the Actions pane, select "Backup and Verify." Result The "SnapManager for SQL Server-Backup" window appears.
5	Optional: To add databases from remote servers or from different SQL instances on the same server to this backup job, click the Federated Backup button, and complete the following substeps: Click Browse. A window opens, displaying all connected servers. Select the server that contains the database you want to add to the backup job. Enter the login details. Click Add. The window closes and the server and all databases therein are displayed as a tree in the top pane. Select the databases that you want to add to the backup job. Select a federated group. SnapManager does not support SAN and NAS databases from the same host in the same federated group. Click Add to Group. The databases are moved into the federated group. Note: You can add databases from multiple servers to the same federated group. Backing up a federated group backs up all databases in that group at the same time. Click OK.
6	Optional: To take an Availability Group backup on single or multiple replicas, in the Databases(s) to back up window, select the databases to be backed up, and complete the following substeps: Click Availability Group Backup. Check either Preferred backup replica only or click Advanced Options. Check Preferred backup replica only to take a backup of only the preferred backup replica. The preferred backup replica is set through the SQL Server 2012 Availability Group properties dialog. Click Advanced Option to take backups on multiple replicas. You can back up only a subset of all of the replicas by setting Replica Type and setting the desired backup priorities. Backup priorities range from a minimum of 1 to a maximum of 100. Click OK.
7	In the "Backup management group" option, select the management group for the backup you want to create: Standard, Daily, or Weekly. For more information, see "SnapManager backup set naming conventions" in How SnapManager backup data is organized and Using backup management groups in backup and verification.
8	Configure your system's up-to-the-minute restore ability. For more information, see "Configuring the number of transaction log backups your system retains" in Managing transaction log backups using SnapManager.
9	If...	Then...
	You want the database backup operation to be immediately followed by a transaction log backup	Select the "Run transaction log backup after full database backup" option.
	You want to schedule the transaction log backup yourself later	See Managing transaction log backups using SnapManager. Note: When you schedule a transaction log backup, ensure that the full backup and transaction log backup do not coincide.
10	If...	Then...
	You want to delete backups older than a specific number of days	Enter the number of days in the "Older than" field
	You want to delete backups more than a specified number of backups	Enter the number of backups in the "In excess of" field
11	If you want to verify databases after the backup operation, select "Verify databases after backup."
12	If you want to run a command or script prior to performing the backup or after the backup finishes, select the "Run Command" option. You can run a command after performing a backup to automatically archive the backup. Result If you select this option, SnapManager displays the Run Command dialog box. For more information, see Pre-command and post-command script settings.
13	Under SnapMirror options, select the corresponding check box if you want to update SnapMirror after operation or to verify available SnapMirror destination volumes. Note: If the system is configured for SnapMirror replication, only the databases on mirrored volumes will be updated on the SnapMirror destination volumes.
14	Under Backup archiving options, select the options to archive the backups using SnapVault.
Back up now or schedule for later
15	You can either run the backup now or schedule it for later. Click one of the following tabs: Backup Now Schedule
To complete this procedure by scheduling the backup:
16	If you select "Schedule...", complete the procedure by scheduling the backup. For details, see Scheduling a backup job or a database verification job.
To complete this procedure by starting the backup:
17	If you select "Backup Now..." do the following: Read the items displayed in the Backup Task List. This list shows the progress of the backup operation after you start it. When you are ready to start the backup operation, click Start Now. Result The backup operation is performed, and each item in the Backup Task List is checked off as the task is complete. You can toggle the Backup Status dialog box between two different views: Backup Task List view and Backup Report view. The Backup Report view displays detailed progress information as the backup progresses. You can also print this information by using the Print Report button. If the backup is successful, the Backup Task List view shows the check-off list with the tasks completed. If Notification is enabled, an email is sent and the event is posted to the Windows Application event log.

Full database backup using the Backup wizard

To start or schedule a full database backup using the Backup wizard, complete the following steps.

Note: For a list of information you need to provide as you complete these steps, see the section "Information you need to specify for a full database backup" which appears earlier in this topic.

Step	Action
1	In the SnapManager for SQL Server console root, click the SnapManager Backup wizard icon. Result The SnapManager Backup wizard starts and displays the Welcome screen.
Welcome
2	Click Next. Result The Databases to Backup or Verify screen appears. The Microsoft SQL Servers navigation tree in the left panel lists the SQL Server databases that are managed from the current SQL Server. Databases that reside on the same storage system and storage system volume are shown with disk icons of the same color.
Databases to Backup or Verify
3	In the left panel, click to select the databases you want to backup. You can back up all databases on an SQL server by selecting the server instead of selecting individual databases. When you select the server, even databases created after configuring the backup are backed up. If you have more than one SQL instance, you must repeat this process for each instance; however, instead of the selecting the server, you should select the instance. When you select a database, SnapManager automatically selects all other databases that reside on the same storage system volume. For information about deselecting any automatically selected databases, see the bullet "Which databases you want to backup" under "Job-specific parameters" in Managing transaction log backups using SnapManager. When you select databases at the SQL Server instance level, SnapManager lists any offline databases as skipped in the backup report. For more information, see the section "Information you need to specify for a full database backup" which appears earlier in this topic.
4	Click Next. Result The Backup or Verify Databases and Transaction Logs screen appears.
Backup or Verify Databases and Transaction Logs
5	Select the Backup Databases and Transaction Logs option, and then click Next. Result: The Select to Apply Backup Option window appears. Note: If you do not select the Backup Databases and Transaction Logs option and select to schedule the transaction log backup yourself, ensure that the full backup and transaction log backup operations do not coincide.
Backup Option
6	If you want to...	Then...
	Add databases from remote servers or from different SQL instances	Select "Federated Backup Options." For more information, see Step 5 in "Full database backup using Backup and Verify" which appears earlier in this topic.
	Take backups of single or multiple replicas of an Availability Group	Select "Availability Group Database Backup, and then select from Preferred Backup Replica Only, Primary, Secondary, All and optionally, Backup Priority.
	Only back up databases from the selected server	Select "Continue with selected databases."
Select SQL Server backup Type
7	Select the Full Database Backup option, and then click Next. Result The "Select backup management group for this backup" screen appears.
Select backup management group for this backup
8	Follow the instructions in the remainder of the Backup wizard screens. The following screens enable you to specify the details of a full database backup: Backup Management Group Backup Transaction Log After Full Database Backup Delete the Oldest Full Backups Retain Up-to-the-Minute Restore Ability for Older Backups Note: This screen appears only if you selected the Delete the Oldest Backups option in the previous screen. Verify the Databases in this Backup View or Change Verification Settings Note: This screen appears only if you chose to automatically verify the databases when the backup is created. SnapMirror options and Backup archiving options (SnapVault) Note: This screen appears only if any SQL Server databases or SnapInfo directories reside on a SnapMirror source volume. Advanced Backup Options Run a command or script with the current operation For a list of information you need to provide, see the section "Information you need to specify for a full database backup" which appears earlier in this topic.
Backup Finish
9	The "Backup Finish" screen prompts you to choose whether you want the operation to be performed immediately or scheduled for a later time.
	If you want to...	Then...
	Run the backup now	Go to Step 10.
	Schedule the backup for later	Go to Step 12.
To run the backup now:
10	If you want to run the backup, Click Finish. Result The Backup Status screen appears and displays the backup settings you have selected.
11	In the Backup Status window, click Start Now. Result The backup is performed and the backup set is written to the volume. The Backup Status dialog box appears and displays a Backup Task List that is used to show the progress of the backup operation after you start it. SnapManager Backup completes each task and checks it off on the list shown in the Backup Task List view. You can switch back and forth between the task check-off list and the progress report using the Switch buttons on either view. If the backup is successful, the Task window shows the check-off list with the tasks completed. If Notification is enabled, an email is sent and the event is posted to the Windows Application event log.
To schedule the backup for later:
12	If you want to schedule the backup for later, do the following: Select the Schedule option. In the Job Name box, enter a name for this job. If you want this job name to overwrite a job of the same name (if it exists), select the Replace Job if Exists option. For more information, see Scheduling a backup job or a database verification job.
13	Under "Select the Scheduling Service to Create Job," select either SQL Server Agent or Windows Scheduled Tasks. For more information, see "Scheduling a backup job or a database verification job.
14	Click OK. If your backup job is not scheduled, you are taken to the Microsoft SQL Server Management Studio for scheduling. You cannot use the option Windows Scheduled Tasks if your backup job is not scheduled.
15	After the job is scheduled, SnapManager exits the Backup wizard.