White Papers

38 TR1059 | V4.0 | Exchange 2013 Data Protection with EqualLogic Auto-Snapshot Manager/Microsoft Edition 4.6 and PS
Series Arrays
D Remote host verification setup
You can optionally perform Checksum Verification and Soft Recovery on a remote host. Remote Host
verification requires the following configuration:
Two host systems with the same installed versions of the following application software:
Auto-Snapshot Manager.
Exchange Management Tools.
A shared network folder or drive to provide a Smart Copy repository.
One of the hosts acts as the
creator server, creating Smart Copies, The second host acts as the
verification server running a Global Verification Task that verifies all unverified Exchange Smart Copies.
The Global Verification window can differ between the local and remote servers. For example, you might
configure verification during an off-peak Global Verification window on the creator server, such as the
default 8:00PM to 6:00AM window. You might then configure the creator server to run verification on the
remote host, setting the verification server’s Global Verification window to 24 hours.
Note: If you want to run Checksum Verification and Soft Recovery on a remote host and your
configuration consists of a HIT Group with two or more hosts, Dell recommends that you use the
following guidelines:
• If your HIT Group is a DAG, then each node will have its own, unique backup document directory.
Because of this, each node will require its own remote host for Checksum Verification and Soft Recovery.
For example, if your HIT Group is comprised of a 4-node DAG, then you will need to allocate 4 separate
hosts for remote host Checksum Verification and Soft Recovery (1 host per node).
D.1 Using a system as a dedicated verification server
To make the best use of system resources, you can configure a host to run only the Global Verification
Task, taking the Checksum Verification and Soft Recovery workload off your production servers. You
specify a Global Verification window that is specific to the verification server, typically a much longer time
period than for a production server.
Using a dedicated verification server enables you to process a greater number of Smart Copies, improving
your recovery options and service level. The verification server might be co-located with Smart Copy
creator servers, or it might be at a geographically remote location. However, the verification server
requires access to the SAN on which you create and maintain Smart Copies.