Remote verification

Benefit of remote verification  

Database verification is CPU-intensive for the host running the verification. To prevent verification from affecting the performance of your production Exchange server, you can run verification on another computer.

Overview of remote verification  

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 filer (FCP or iSCSI).

The process followed for remote verification is outlined in the following table.

Note
Whether you run verification remotely or locally, the verification is performed on a LUN backed by snapshot. If you take a snapshot of the same volume while a LUN backed by snapshot exists, you create a "busy snapshot," which might cause problems when you attempt to delete some snapshots. For this reason, you must be careful not to schedule backups while a verification is in progress.

The connectivity required to perform remote verification is shown in the following diagram:

Requirements for a remote verification server for Exchange 2000 or 2003  

To run remote verification for Exchange 2000 or 2003, your remote Windows system must meet the following requirements:

• SnapDrive must be installed.

  Caution
  Do not try to connect the Exchange server's LUNs to the remote verification server.

• If you are using iSCSI to connect to the filer on the remote verification server, an iSCSI connection must be created.
• SnapManager must be installed.

  You need to install, but not configure, SnapManager. You can use the same user account you used for the production server.

• The correct Microsoft binaries must be installed.

  Microsoft requires that the Microsoft Exchange System Management Tools be installed on remote verification machines for licensing compliance. However, the minimum configuration required by SnapManager is to copy the following files from the Exchsrvr\bin directory on your Exchange server to the verification server:

  • eseutil.exe
  • ese.dll
  • jcb.dll
  • exosal.dll
  • exchmem.dll

  For more information about performing verification on a computer that does not have Exchange installed, see Microsoft KB article 244525.

  Note
  The version of eseutil must match the version of Exchange. When you apply an Exchange service pack to the production server, you must copy over a new version of eseutil at the same time, or else verification cannot function correctly.

Requirements for a remote verification server for Exchange 5.5  

To run remote verification for Exchange 5.5, your remote Windows system must meet the following requirements:

• SnapDrive must be installed.

  Caution
  Do not try to connect the Exchange server's LUNs to the remote verification server.

• If you are using iSCSI to connect to the filer on the remote verification server, an iSCSI connection must be created.
• SnapManager must be installed.

  You need to install, but not configure, SnapManager. You can use the same user account you used for the production server.

• The esefile utility must be copied from the Support folder in Exchange 5.5 SP4 to the SnapManager installation directory.

  Note
  The version of esefile must match the version of Exchange. When you apply an Exchange 5.5 service pack to the production server, you must copy over a new version of esefile at the same time, or else verification cannot function correctly.

Designating a remote verification server  

To designate a remote verification server, complete the following steps on the production Exchange server.

Copyright © 1994-2004, Network Appliance, Inc. All rights reserved.
Part No. 215-00858
File: manage5.htm
Last updated: Tue Jun 15 15:34:11 2004