HP Storage Mirroring Software - Manual (Page 237)

Workload protection Page 236 of 677
l
The servers must have the same named instances, unless you are
running Application Manager in advanced mode. In this case, you can
identify instances to protect that are offline or do not exist on the target.
The Manage SQL Server Instances dialog will only appear if you two or
more SQL instances (default plus one or more named instances or two
or more named instances with no default instance).
l
The TcpPort for the named instances will be different. This is
acceptable.
l
You can exclude user databases from protection, but the system
databases (except for tempdb) are required.
l
You may want to exclude the tempdb database to reduce mirroring and
replication traffic.
l
Transparent Data Encryption (TDE) is supported for SQL 2008,
however the SQL service must be running with the same service
account on the source and target.
l
Database Only—This option will protect the .mdf, .ldf, and .ndf files. With this
option, the databases will be attached to the target in the event of a failure
and then end-users an access the data. This option is intended for advanced
users only. During the validation process, you will have the opportunity to
transfer user logins and permissions (both server and database-level) and
certain SQL Server registry and configuration settings to the target server.
This will allow users to access the data associated with the selected
database(s), but no other server-level functionality will be transferred to the
target server, including but not limited to Job Server configuration, Full-Text
service configuration, SQL Replication configuration, linked servers, remote
servers, and backup devices.
With this option, the source and target servers must have the following
configuration.
l
You must configured any SQL Server replication on the protected
source databases on the target after failover.
l
Transparent Data Encryption (TDE) is not supported for SQL 2008
when using database only mode.
l
Attempting to attach a replicated SQL database on the target server
after failover outside of the Application Manager can fail.
l
The Storage Mirroring service account (typically the target's
LocalSystem account) is the account used to attach and detach
databases on failover and failback. When the database is detached by
the failover and failback scripts, the Storage Mirroring service account
becomes the owner of those files that make up the database (*.mdf,