HP Storage Mirroring Software - Manual (Page 553)

551 of 739
Failing back using DNS
If you have not done so already, launch the 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).
During failover and failback, the status messages at the bottom of the screen describe
the failover or failback progress.
Note:
●
Protection Status and Monitoring Status on the Setup tab are not updated
during failback.
●
The refresh update rate is not automatically updated during failback.
●
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.
Failback and restoration
After issues on the source server are resolved and it is connected and online, you can
failback to the source and restore any modified data. In order to initiate failback, both the
Protection Status and Failover/Monitoring Status must be Failed Over.
Note:
When using Application Manager for Exchange, any mail stores or storage
groups that are created while the source is in a failover state will not failback
properly.
If the source server has to be rebuilt, follow the instructions in Rebuilding the source