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

521 of 739
the stores manually and run the Replace replicas PowerShell call from the
failover script to update the PF replicas (if applicable).
● After failover, linked databases in the SQL instance will be unavailable
until the service master key is updated. After failover, you will need to run
the command “alter service master key force regenerate” against the SQL
target server to reset the service master key, then remove and re-add the
linked servers into the target SQL instance.
● In SQL Server Database-only mode, after failover with snapshot is
finished the SQL Server 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, then
manually attach the databases.
● After failing over in a SQL Workgroup (no DNS), you will not be able to
connect to the source server instance of SQL. You can work around this
issue by creating an alias on the target with the source server’s name.
● After failing over a SQL 2008 source to a SQL 2008 target, Rich Internet
Applications created using ADO.net 2 may not connect.