Verification of the databases in a backup set can be done on the production Exchange server (the Windows host system running the Exchange server used to service the end users) or on a remote verification system (a different Exchange server with Exchange management tools installed).
Running database verification on a production Exchange server is CPU-intensive for the Windows host and also involves a substantial amount of activity on the storage system. SnapManager offers three methods for managing database verification load:
The three options for managing database verification load, which can be used separately or in any combination, are described in Managing database verification load.
Note
Both deferred verification and remote verification manage database verification load by separating database verification from the backup operation. Verification throttling manages database verification load by slowing down the verification throughput rate.
This topic provides detailed information about remote verification. For more information about remote verification, see the following topics:
Note
When you change the database verification server, this change does not affect any database backup (with verification) or database verification-only jobs that are already scheduled. You will need to recreate the scheduled backup jobs.
The following paragraphs describe the prerequisites for using a remote verification server.
Remote verification is performed using the same mechanisms used for local verification, except that the verification is performed on a different host than the one that initiated the backup. This is why you need SnapDrive and SnapManager installed on your remote verification server, as well as connectivity to the storage system (FCP or iSCSI). The requirements for a remote verification server are described in Requirements for a remote verification server.
If you use a remote verification server to verify the databases in multiple databases in a single job, an additional LUN is required. For more information, see Verifying multiple backup sets using a remote verification server.
To designate a remote verification server, see Viewing or changing the verification server.
The following list of steps outline the process followed for remote verification.
Note
Whether you run verification 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.
To view or change the verification server, complete the following steps from the production Exchange server.
| 1 |
Connect to the production Exchange server, and then open the Database Verification Settings dialog box. |
|
|
Go to the Verify the Databases and Transaction Logs in this Backup screen, and then click Verification Settings. | ||
|
Go to the Verify Database Integrity in the Selected Backup screen (displayed only if you choose to restore from an unverified backup, and then click Verification Settings. | ||
ResultThe Database Verification Settings dialog box appears. The Verification Server tab is active by default and displays the host name of the current verification server. |
||
| 2 |
In the Verification Server box, type or browse to the Exchange server you want to use as the database verification server. Note |
|
| 3 |
ResultThe Verification Settings dialog box closes. Note |
|
Copyright © 1994-2006, Network Appliance, Inc. All rights
reserved.
Part No. 215-01873_A0
File: cfgappl6.htm
Last updated: 28-Mar-2006 11:31:12