4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

A profile is a container consisting of the SQL data (that is, databases and logs) and
the corresponding registry setting necessary for starting an instance of SQL Server.
The Active-Passive architecture uses an “N+1” model in which there is a local profile
(an “N” profile”) for each node participating in the Virtual SQL Server plus a cluster
profile (the “+” profile) that runs on the active node for the Virtual SQL Server.
For example, in a two-node cluster there are three profiles: the two local profiles (N)
and a clustered profile (+1). The clustered profile can move around the cluster, and
when mounted on a node, it turns the state of the node from passive to active. At
any one point in time, the node running with the clustered profile (the “+1” profile)
is the active node and all other nodes are passive (that is, running with their local
“N” profiles).
On the PolyServe Management Console, the active node is specified as the primary
node and the passive nodes are specified as backup nodes. Throughout this guide,
the primary and backup designations are used to refer to the active and passive
nodes.
Plan Your SQL configuration
Before installing SQL Server, it is important to determine how the SQL Server instances
should be configured across the matrix. First determine the number of SQL instances
that you will need. These instances can be installed on any node in the matrix.
Next, determine how you want to associate the instances with Virtual SQL Servers.
You could use a separate Virtual SQL Server for each instance, you could assign all
of the instances on a node to a single virtual server, or you could use some other
scheme.
Then determine how you want to configure the Virtual SQL Servers. Each Virtual SQL
Server needs a primary node and one or more backup nodes. The backup nodes
for each Virtual SQL Server must contain the same set of SQL instances as the primary
node. Following are some sample configurations.
NOTE:
A primary SQL instance and its backup SQL instances must have the same name.
For example, if you install an SQL instance called “instance1” on the primary node,
you will also need to install an instance called “instance1” on the backup node.
Introduction10