HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

610 of 739
Verify target data viability
If you have not done so already, launch the Application Manager.
Note:
Target data verification can only be used with Exchange and SQL.
In order to use target data verification, the target server must be running
Storage Mirroring Recover version 5.2 or later.
If the target server is on a cluster, the Target Data Verification feature is
not available.
In a workgroup (with no DNS), Target Data Verification for SQL is not
supported.
After you have configured your servers, you can use the Application Manager to run a
test that verifies that the database on the target is viable for failover. One benefit of
performing the verification test is that you do not have to perform an additional remirror or
failover to verify target data viability.
In order to perform target data verification, the following prerequisites must be met:
The target server must be running Windows 2003, Service Pack 1 or later.
If the current volumes do not have adequate space to contain the snapshots,
modify the properties for the Shadow Copies settings on each volume to set the
storage location of the snapshots where the data resides.
Target path blocking must be disabled for the connection in the Replication
Console.
The Storge Mirroring disk queue cannot be located on a volume that will be
reverted. To use target data verification, you must first update the queue setting in
Replication Console, then restart the Storage Mirroring service.
For Exchange, if you are running the Application Manager from any server other
than the source or target, you must install the Exchange System Manager
component on that client (due to a dependency on the cdoexm.dll file).
For SQL, target data verification is only supported in instance mode. It is not
available for database-only mode.
While in verification mode, Storage Mirroring Recover will queue on the target in
the directory you selected during Storage Mirroring Recover configuration. You
should be aware of your data change rate and make sure you have adequate
capacity on the volumes configured for the Storage Mirroring Recover target
queues.