If you created a database backup Snapshot copy without automatically verifying the databases at the time the backup was created, you can verify the databases in that backup as a separate operation. See the following topics for more information:
Attention
If you attempt to perform a database verification (or a backup with database verification) when SnapManager is running from a Terminal Services client instead of from a system console, the operation will fail.
A database integrity verification job is specified using a combination of parameters.
Each time you start or schedule a database verification, you must specify the following information in either the Backup Wizard or in the Backup and Verification tab:
For more information, see Using backup management groups in backup and verification.
Note
If you request verification of a greater number of unverified Snapshot copies than specified by your database and backup management group selections, the verification will proceed, and therefore all backups will be verified.
This feature is typically used to automatically archive a backup, as described in Using Run Command After Operation to archive automatically.
Note
If you want to schedule the verification to run later, you also need to know the job scheduling information.
The following list summarizes the settings that pertain to database verification:
This is configured using the Verification Server tab of the Database 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
Whether you run database verification either remotely or locally, the verification is performed on a LUN backed by Snapshot copy. If you take a Snapshot copy of the same volume while a LUN backed by Snapshot copy exists, you create a "busy Snapshot copy," which might cause problems when you attempt to delete some Snapshot copies. For this reason, you must be careful not to schedule backups while a verification is in progress. For information about busy Snapshot copies, see Problem deleting backups due to busy Snapshot copy error.
For more information, see Selecting the Snapshot copy access method for database verification.
For more information, see Configuring Eseutil throttling for database verification.
For more information, see Overriding database verification during restore.
To run or schedule database verification, complete the following steps from the production Exchange server (not from the remote verification server).
| 1 |
On the production Exchange server, click the Backup and Verification tab. |
| 2 |
Select the storage group (Store) you want to run the verification on. |
| 3 |
Select the Verify Databases and Transaction Logs in the Most Recent Unverified Backups option.
|
| 4 |
Select how many of the most recent unverified backups you want to verify. Note |
| 5 |
In the Backup Management Group field, select the backup management group of the backups you want to verify. If you want to verify the most recent backups regardless of their backup management group, select All. |
| 6 |
If you want to run a command after the verification is complete, select the Run Command After Operation check box. This is usually done to archive backups. For details, see Using Run Command After Operation to archive automatically. |
| 7 |
If your volume is a SnapMirror source volume and you do not want the destination volume to be updated after this verification is complete, clear the Update SnapMirror After Operation check box. |
| 8 |
Click Verify Now, and on the Backup Status window, click Start Now. Note ResultVerification is run on the databases in the backup you selected. If verification is successful, a dialog box appears telling you so. If any backup database fails verification, delete that backup and create another. |
Copyright © 1994-2006, Network Appliance, Inc. All rights
reserved.
Part No. 215-01873_A0
File: backup4.htm
Last updated: 28-Mar-2006 11:31:01