HP Storage Mirroring Software - Manual (Page 522)

520 of 739
Application failover
If you have not done so already, launch the Storage Mirroring Recover Application
Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring
Recover Application Manager.
There are two options for how to perform failover:
●
If you selected DNS failover , you can use the Application Manager to automate
failover.
●
If you selected Identity failover , you will need to use a manual process for failover.
If you are using a standalone BlackBerry server with Exchange or SQL, there are
additional steps so that the BlackBerry server will recognize when the server that has the
BESAdmin account has been failed over
If an error occurs during failover, a message box will appear. You can use the Actions
menu to launch the failover log file.
Note:
●
If you open the Application Manager and try to select a source that is
currently down, a prompt will appear stating that the source was not
available and that if the source is failed over, you should first select the
target. If you select the target, then select the source (as recommended in
the prompt), the same prompt appears (though you would expect to get a
prompt to failover).
●
You cannot use the Application Manager to failover until a failover
condition has been met in accordance with the failover monitor settings
set when you configured protection.
●
In a clustered failover scenario where the source suddenly becomes
unavailable (crashes), if the Application Manager is open, it may appear to
"hang" or pause for up to 30 minutes before the process will continue.
This is caused by the Application Manager waiting on the msclus.dll to
respond. To reduce the amount of time before failover can continue, close,
then re-open the Application Manager interface.
●
If you are using Outlook Web Access or Outlook 2007, after failover a
security alert is displayed. This is because the certificate has the source
server name but is now on the target. Click Allow or OK to dismiss the
alert.
●
If an Exchange 2007 environment has more than one domain controller
and the domain controller that Exchange is using changes during the
failover process, stores may not mount during failover. To work around
this issue, either modify the failover script to use the domain controller that
Exchange uses when the Information Store service is started; or, mount