HP OpenView Storage Mirroring High Availability for Exchange Server 2000/2003 Application Notes (May 2005, T2558-88020)

Storage Mirroring High availability for Exchange Server 2000/2003 application notes 25
15.If you accepted the default installation on the original source (before it failed), set Microsoft Exchange
Messaging and Collaboration Services and Microsoft Exchange System Management Tools to Disaster
Recovery.
NOTE: Because the Exchange disaster recovery installation is configured for tape backup recovery,
informational messages such as those below do not apply to this configuration and can be disregarded.
Use Exchange Admin Snap-in to ensure that you have a valid Exchange Server Object for this server for
which you are running setup in recovery mode.
After setup has completed, restore your databases from backup, then reboot your machine.
16.During the post-installation processing, the installation may stall while trying to start the System
Attendant (MSExchangeSA) service. It should take no more than a couple of minutes to start this
service. If it takes longer, use the Windows Task Manager to terminate the setup process. This will not
affect your ability to start services on the target after a failure.
17. Install any Exchange service packs or patches.
18.Stop all of the Exchange services on the source so that you can overwrite the data with the newer data
on the target. The services must be stopped in the order identified in the pre-failback script. See
”PreBack.BAT” on page 11.
19.To complete this process, continue with step 8 under ”Recovering to the original source” on page 17
and complete the remaining steps in that section.
Appendix 3: Configuring additional Exchange
Failover utility options
In order for a mail store (and its users) to be failed over (or failed back), a mail store on the source must be
paired to a mail store on the target. In order to be a valid pair, the database filename (excluding path
information) of these two stores must match. The Exchange Failover utility uses two methods to make these
mail store pairs. The simplest (default) method requires that the database filenames be unique and that
each filename only occurs once on the source and once on the target. This is the case for the example
script provided in ”Configuring failure monitoring” on page 9. If your environment uses the same store
name in different groups or if you need to rename stores or groups on the target during failover, you will
need to add additional options to the Exchange Failover utility used in the postover.bat script.
For example, a server called ExchSrvr contains two mail groups Indy and Boston. Each group contains a
mail store called Sales. In its simplest form, the Exchange Failover utility would not know which group to
associate the Sales mail store with since it is based on the database file name.
To resolve this issue, you can direct the groups and mail stores to meet your environment needs. The -r
option in the Exchange Failover utility is a pairing rule. It allows you to specify how the groups and mail
stores on the source will be paired on the target.
Source: ExchSrvr
Group: Indy
Group: Boston
Mail store: Sales
Mail store: Sales
Target: ExchSrvr_Bkup
Group: Indy
Group: Boston
Database file: Sales?