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

522 of 739
Failing over using DNS
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.
Based on the current protection status and/or failover state, the Failover/Failback button
on the Monitor tab and menu options will be updated to display the available command.
If the Application Manager is not in a state that will allow failover or failback to be
executed, the Failover/Failback button and menu option will be grayed out (disabled).
In the Application Manager, there are two ways that failover can be initiated:
Automatically, when a failover condition has been met (such as if the source has
gone down)
Manually (for instance, when you want to do maintenance or upgrades on the
source server)
In order to initiate either an automatic or manual failover, the source and target servers
must already be configured so that the Protection Status is Protected and Monitoring
Status is Enabled.
During failover, the status messages at the bottom of the screen describe the failover
progress.
Note:
Protection Status and Monitoring Status on the Setup tab are not updated
during failover.
The refresh update rate is not automatically updated during failover.
When using Application Manager for Exchange:
If your SMTP gateway (or vendor) is configured to send mail to a
specific IP address and that IP address is not failed over to the
target, you will need to change it during failover.
While in a failed over state, you cannot log in to the domain from the
source Exchange server. This is because the target has assumed
the source server's host Service Principal Names to allow Outlook
Web Access to be accessed using the source name. If you need to
log in to the domain and OWA is not needed, contact HP Technical
Support for a workaround.
When using Application Manager for file servers, the failover button will
only work after the source server is offline. This is necessary to prevent
name conflicts on the network when the name is failed over.
Initiating automatic failover