HP Storage Mirroring Software - Manual (Page 482)

Failover Page 481 of 677
After failover is complete, clients will be rerouted to the target, which is standing in for the
source.
Exchange Note: Users using Outlook or Outlook Web Access to receive e-mail can
connect after the changes have propagated through your
environment. Users that had Outlook open during failover will need to
restart the Outlook client (excluding Outlook Web Access clients on a
LAN). Additionally, those users using Outlook Web Access or
Outlook 2007 may see a security alert because the security certificate
has the source server name but Exchange is now on the target. Click
Allow or OK to dismiss the alert.
You will not be able to log in to the domain from the source Exchange
server after failover because the target has assumed the source
server's host Service Principal Name so that Outlook Web Access
can use the source name. If you need to log in to the domain and
Outlook Web Access is not needed, contact technical support for a
workaround.
If you SMTP gateway is configured to send e-mail to a specific IP
address that address is not failed over to the target, you will need to
update the IP address after failover.
Mail stores or storage groups created after a failover will not be failed
back.
SQL Note: After failover, linked databases in the SQL instance will be
unavailable until the service master key is updated. You will need to
run the command "alter service master key force regenerate" against
the SQL target server to reset the service master key and then
remove and re-add the linked servers into the target SQL instance.
After failover with a snapshot of a SQL database-only server, the SQL
services on the target server are stopped and the databases are not
mounted. You will need to manually start the MSSQLServer service
for each instance on the target server and then manually attach the
databases.
After failing over SQL 2008, Rich Internet Applications created using
ADO.net 2 may not connect.