SnapManager provides two ways for you to start or schedule a full database backup: using the Backup Wizard or using the Backup and Verification tab. See the following topics for more information:
A full database backup operation is specified using a combination of parameters.
Each time you start or schedule a full database backup, you must specify the following information in either the Backup and Verification tab or in the Backup Wizard.
When you select one database, SnapManager automatically selects all other databases that are located on the same Data ONTAP storage volume. SnapManager allows you to deselect automatically selected databases as follows:
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 will progress as follows:
If the databases on the LUNs on Data ONTAP storage volumes are moved to local disk later, the previously scheduled backup operation will skip backup deletion. In this case, the backup operation will need to be re-created and rescheduled in order for backup deletion to proceed for future operations.
Note
For an instance-level transaction-log-only backup operation in which one of the selected databases cannot be backed up, the operation will proceed in the same manner as described above.
If an SQL Server 2005 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 filegroups of the database.
For details, see Using backup management groups in backup and verification.
For a description of this option, see Automatic deletion of the oldest backups in a management group.
For a description of this option, see Option to retain up-to-the-minute restore ability.
Note
Although it is possible to restore from an unverified backup, NetApp strongly recommends that you restore only from verified backups.
This feature is typically used to automatically archive a backup, as described in Automatically archiving SnapManager backups using SnapVault.
For more information about this option, see Replicating Backups to Mirrored Volumes.
Note
If you want to schedule the backup to run later, you also need to know the job scheduling information.
The following list summarizes the backup settings that pertain to full database backups:
For more information, see SnapManager Snapshot naming conventions.
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 tab of the Backup Settings dialog box, described in Configuring the profile of a full database backup.
The Backup Settings dialog box can be accessed from the Backup and Verification tab, as well as from the Backup Wizard.
The following list summarizes the settings that pertain to database verification:
This is configured using the SQL Server tab of the Verification Settings dialog box, described in Selecting the database verification server. 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.
Note
Database verification is performed on a LUN backed up by Snapshot copy. If you create a Snapshot copy of the same volume while a LUN backed by Snapshot copy exists, you 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:
For information about busy Snapshot copies, see Busy Snapshot error prevents deletion of backup set.
This is configured using the DBCC Options tab of the Verification Settings dialog box, described in Selecting DBCC options.
The Verification Settings dialog box can be accessed from the Backup and Verification tab, as well as from the Backup Wizard:
Note
The View or Change Database Verification Options screen appears only if you are specifying a "Full database backup operation" or a "Verify most recent Snapshot copy backups" operation; the SnapManager Backup Wizard does not present this screen if you are specifying a "Transaction log backup only" operation.
To start or schedule a full database backup using the Backup and Verification tab, 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 finished. If you want to back up only transaction logs, see Creating a transaction log backup using SnapManager.
Note
For a list of information you need to provide as you complete these steps, see Information you need to specify for a full database backup.
| 1 |
In the SnapManager main window, click the Backup and Verification tab. ResultThe Backup and Verification tab is activated. 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 filer volume are shown with disk icons of the same color. |
|
| 2 |
In the left panel, 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 filer volume. For information about deselecting any automatically selected databases, see the bullet "Which databases you want to back up" under Job-specific parameters. When you select databases at the SQL Server instance level, SnapManager will report any offline databases as skipped in the backup report. For more information, see Information you need to specify for a full database backup. |
|
| 3 |
In the Types panel, select the Full database backup option. ResultThe Options subpanel provides a choice of backup options that pertain to full database backup operations.
|
|
| 4 |
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 Snapshot naming conventions and Using backup management groups in backup and verification. |
|
| 5 |
If 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. |
|
| 6 |
If you want to automatically delete older backups within the selected backup management group, do the following: Selecting this option enables you to manage the number of Snapshot copies for a given backup management group. For more information, see Automatic deletion of the oldest backups in a management group. |
|
| 7 |
If you choose to automatically delete older backups within a backup management group, you are also given the option to ensure that this is done without creating a break in the continuity of transaction logs between the previous backup and the present time. By limiting the automatic deletion of backups in this way, you retain the ability to use the older backups in an up-to-the-minute restore. To use this option, select the "Retain up-to-the-minute restore ability for older backups in other management groups" option. For more information, see Automatic deletion of the oldest backups in a management group. |
|
| 8 |
If you want the full database backup to be followed by a database verification, select the "Verify Snapshot after backup (run DBCC)" option. Otherwise, be sure to verify the backup later, as described in Chapter 9, Performing database verification using SnapManager. Note |
|
| 9 |
If you want to run a command after the backup finishes, select the Run Command After Operation option. This is usually done to archive backups. Note |
|
| 10 |
If the databases reside on a SnapMirror source volume and you want the destination volume to be updated after this backup finishes, select the Update SnapMirror After Operation option. Note |
|
| 11 |
You can either run the backup now or schedule it for later. Click one of the following buttons: |
|
| 12 |
If the Run Command After Operation dialog box appears, specify the command and then Click OK to close the dialog box. For details, see Using the Run Command After Operation dialog box. |
|
| 13 |
If the Schedule Job dialog box appears, complete this procedure by scheduling the backup. For details, see Scheduling a backup job or a database verification job. |
|
| 14 |
If the Backup Status dialog box appears, do the following: ResultThe backup operation is performed, and each item in the Backup Task List is checked off as the task is finished.
|
|
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 Information you need to specify for a full database backup.
| 1 |
In the SnapManager for SQL Server main window, click the SnapManager Backup Wizard icon. ResultThe SnapManager Backup Wizard starts and displays the Welcome screen. |
|
| 2 |
ResultThe Databases to Back Up 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 filer volume are shown with disk icons of the same color. |
|
| 3 |
In the left panel, click to select the databases you want to back up. 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 back up" under Job-specific parameters. When you select databases at the SQL Server instance level, SnapManager will list any offline databases as skipped in the backup report. For more information, see Information you need to specify for a full database backup. |
|
| 4 |
ResultThe Back Up or Verify Databases and Transaction Logs screen appears. |
|
| 5 |
Select the Back Up Databases and Transaction Logs option, and then click Next. Result |
|
| 6 |
Select the Full Database Backup option, and then click Next. Result |
|
| 7 |
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:
For a list of information you need to provide, see Information you need to specify for a full database backup. |
|
| 8 |
The When to Run this Operation screen prompts you to choose whether you want the operation to be performed now or scheduled for a later time. |
|
|
Go to Step 9. | ||
|
Go to Step 12. | ||
| 9 |
If you want to run the backup now, do the following: ResultThe Completing the Backup Wizard screen appears and displays the backup settings you have selected. |
|
| 10 |
After you verify that all the settings in the window are correct, go to the Completing the Backup Wizard dialog box and click Finish. ResultThe Backup Wizard closes and the Backup Status window appears and displays a Backup Task List that will be used to show the progress of the backup operation after you start it. |
|
| 11 |
In the Backup Status window, click Start Now. ResultThe backup is performed and the Snapshot copy is written to the volume.
|
|
| 12 |
If you want to schedule the backup for later, do the following: For more information, see Scheduling a backup job or a database verification job. Result |
|
| 13 |
In the Select the Scheduling Service screen, do the following:
ResultThe Completing the Backup Wizard screen appears and displays the backup settings you have selected. |
|
| 14 |
After you verify that all the settings in the window are correct, go to the Completing the Backup Wizard dialog box and click Finish. ResultThe selected scheduler displays a dialog box. |
|
| 15 |
To schedule the job and close the Backup Wizard, do the following: |
|
When attempting to back up multiple databases concurrently, the operation might fail due to lack of a sufficient number of worker threads.
The backup failure is accompanied by one of the following error messages:
The number of databases selected for concurrent backup exceeds the maximum number of SQL server worker threads that are available on the SQL server ServerName to perform this backup. Please increase the number of worker threads for SQL server ServerName to be greater than the sum of the worker thread required to service SQL client and the number of databases connected to SQL server ServerName, which are selected for concurrent backup. Using Enterprise Manager, the maximum number of worker threads can be configured from the Processor tab in the properties window for the SQL server ServerName.
Decrease the number of databases being backed up concurrently.
Increase the maximum number of worker threads for this SQL Server.
To implement either or both of the preceding workarounds, complete the following steps.
| 1 |
Start the Configuration Wizard, then step through the following screens without specifying any configuration changes: |
|
| 2 |
If you want to decrease the maximum number of databases that can be backed up concurrently for each SQL Server instance (as described in Workaround 1), decrease the value in the "Maximum databases..." box in the Number of Databases that Can be Backed Up Concurrently screen. For more detailed information, see Using the Number of Databases that Can Be Backed Up Concurrently screen. |
|
| 3 |
If you want to increase the maximum number of SQL Server worker threads (as described in Workaround 2), select the Modify SQL Server "Maximum Worker Threads Parameter" option in the Number of Databases that Can be Backed Up Concurrently screen. For more detailed information, see Using the Number of Databases that Can Be Backed Up Concurrently screen. |
|
| 4 |
The next screen that appears depends on whether you selected the Modify SQL Server "Maximum Worker Threads" Parameter option. |
|
|
You did not select the Modify SQL Server "Maximum Worker Threads" Parameter option |
The SnapInfo Directory Type screen appears. Go to Step 7. | |
|
You selected the Modify SQL Server "Maximum Worker Threads" Parameter option |
The Modify SQL Server Maximum Worker Threads Parameter screen appears. Go to Step 5. | |
| 5 |
Use the Modify SQL Server Maximum Worker Threads Parameter screen to specify whether you want to modify the maximum number of worker threads for any SQL Server instance. You have the following options:
For more detailed information, see Using the Modify SQL Server Maximum Worker Threads Parameter screen. Note |
|
| 6 |
After you have finished viewing and optionally changing this SQL Server parameter, click Next. ResultThe SnapInfo Directory Type screen appears. |
|
| 7 |
Step through the remaining screens of the Configuration Wizard without specifying any further configuration changes:
|
|
| 8 |
In the Completing the Configuration Wizard screen, verify the changes you specified and then click Finish. |
|
| 9 |
In the Configurator Status dialog box, click Start Now to close the dialog box and begin the Configuration Wizard tasks you specified. |
|
| 10 |
When a message box appears and notifies you that the configuration changes completed successfully, click OK to close the message box. |
|
| 11 | ||
Copyright © 1994-2006, Network Appliance, Inc. All rights
reserved.
Part No. 215-01752_A0
File: bkptask3.htm
Last updated: 01-Sep-2006 07:41:15