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

525 of 739
Note:
You cannot cancel or interrupt the failover process.
The length of time needed for a failover depends on the number of users and
how long it takes to start services on the target. For a large number of users, the
failover process could take a while.
Next step:Fail back using DNS
Failing over using identity
If you have not done so already, launch the Application Manager by selecting Start,
Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application
Manager.
The following sections describe the manual processes you can use to manage failover.
These manual processes are required if you chose to perform Identity failover.
You will be using the Replication Console, Failover Control Center, and/or Text Client to
manage identity failover.
Initiating a failover
If a failure occurs and the Failover Control Center Time to Fail counter reaches zero (0),
a dialog box will appear in the Failover Control Center requiring user intervention to
initiate failover. Acknowledge the manual intervention prompt to start failover.
Note:
If the Failover Control Center is not open when the failure occurs, the dialog box
will appear the next time the Failover Control Center is opened and you are
logged on to the target. See Failing over for information on monitoring a failure.
The post-failover script created earlier will automatically run. During failover, Windows
Event Viewer, the Storage Mirroring Recover log, DFO log, and Application Manager
logs record the failover events. When failover is complete, the target will have the
application services started, the databases mounted, and the users pointed to the target.
Note:
The DFO and Application Manager log files are located in the same directory as
the Application Manager.
If you are failing over Exchange, after the changes have propagated through
your environment, clients can connect through Outlook or Outlook Web Access
to receive their e-mail. Users that had Outlook open during the failure will need
to restart the Outlook client (excluding Outlook Web Access clients on a LAN).