HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)
49 of 739
Note:
● If you are using SQL Server, you will be prompted to download and install
the Microsoft SQL Server2005 backward compatibility components. This
package includes the SQLDMO library, which is required to run the
Application Manager.
● You should use the same version and service pack of SQL Server on both
the source and target servers. Exceptions would be that in Database
Only protection mode you may use a newer version of SQL Server on the
target server or have a 32-bit source and a 64-bit target to perform a
failover (for instance, when using Application Manager to facilitate a
migration from SQL Server 2000 on the source to SQL Server 2005 on the
target, or to migrate data from a 32-bit source to a 64-bit target). You
cannot failback when using different versions of SQL Server on the
source and target.
● To enable the Application Manager to work with MSDE (SQL Express 2000) and
SQL Server 2005 Express, Named Pipes and TCP/IP need to be added to the
Enabled Protocols. By default, these are disabled. They must be enabled to accept
remote connections.
● For MSDE, you must run the svrnetcn.exe command, which is located in the
C:\Program Files\Microsoft SQL Server\80\Tools\Binn directory.
● For SQL Server 2005 Express, you must launch the SQL Server
Configuration Manager, expand SQL Server 2005 Network Configuration
, and for Protocols for MSSQLSERVER enable Named Pipes and TCP/IP.
● To use the Application Manager for SQL, the user logged on to Windows must be
a member of the SQL Server sysadmin role on the source and target servers.
● The source and target SQL servers must be in the same domain; otherwise, the
SQL Server service on both the source and target servers must be configured to
start with the same domain user account.
● When setting up SQL servers in a workgroup, make sure the source server's NIC
does not register the IP addresses with DNS.
● In order to protect SQL named instances, both the source and target SQL Servers
must have named instances with the exact same name installed prior to
configuring protection.
● The Application Manager does not support a SQL default instance that has been
configured to use non-default ports.