HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)
526 of 739
If DNS failover was selected, the clients will have to wait for the IP cache to expire, or
type in ipconfig /flushdns in a command window. This time can be adjusted by
lowering the TTL (Time to Live) setting within your DNS server’s configuration. For more
information, refer to your DNS server documentation.
Next step:Fail back using identity
Failing over Exchange or SQL with BlackBerry
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.
If you are using a standalone BlackBerry server with Exchange or SQL, complete the
following steps so that the BlackBerry server will recognize when the server that has the
BESAdmin account has been failed over.
1. Prior to failing over, shut down the BlackBerry server.
2. After failover, bring the BlackBerry server back up.
3. For BlackBerry Enterprise Server3.0:
a. Open a command prompt on the BlackBerry server and cd to C:\Program
Files\Research In Motion\BlackBerry Enterprise Server\Utility.
b. Run the command handheldcleanup –m
c. Run the command handheldcleanup –u
This command will prompt you for the name of the BlackBerry server.
4. For BlackBerry Enterprise Server3.5 through 4.1, see BlackBerry knowledgebase
article KB03296.
The same process should be followed when failing back.
EVS failover
If you have not done so already, launch the Application Manager.
Graceful failover
At the user's discretion, the Application Manager can perform a graceful, or “soft”,
failover. A soft failover means the source cluster remains up and running while the EVS
is transferred to the target cluster. This can be accomplished by using the failover button
in Application Manager. The steps the Application Manager takes to transfer the EVS
from the source cluster to the target are the same as during a site failure failover, which
is described in Site failure failover. The only difference is that in a soft failover, the
source cluster resources are taken offline gracefully.
Site failure failover
If the Application Manager detects that the source cluster has failed completely, it will