3.6.1 HP PolyServe Software for Microsoft SQL Server Release Notes (T5392-96026, August 2008)

clients c an then continue to use the lega cy connection string to access the SQL

database in its new location.

• MSDTC support. MSDTC can now be virtualized or devirtualized on-the-ﬂy.

• Role-based security. Using the role-based security feature provided with Matrix

Server, you can create a role to manage Virtual SQL Servers and Virtual SQL

Instances.

New Activ e-Passive Architecture

In the 3.4 release, MxDB for SQL Server used a Primary-Backup architecture. For

example, when y

ou virtualizedaSQL server instance in atwo-nodecluster,you would

declare one node to be the primary for the instance and the second node to be the

backup. The high-availability engine provided with MxD B for SQL Ser ver would then

create a proﬁle for each node.

Aproﬁle is a co

ntainer consisting of the SQL data (that is, databases and logs) and the

correspondin

g registry setting ne cessar y for starting an instance of SQ L Server. With

the Primary-

Backup architecture, also c alle d the “N m o d el,” the total num ber of proﬁles

for a virtualized SQL instance is equal to the number of nodes par ticipating in the

Virtual SQL Server. If the primary node goes down, the SQL high-availability engine

will mount the proﬁle from that node onto the backup node and then bring up the SQL

instance on that node. Although this architecture provides high-availability, it can be

susceptib

le to duplicate registry issues.

The new Ac

tive-Passive architecture provided with the 3.6 release is very ﬂexible and

highly resistant to the duplicate registry issue. This new architecture provides a n “N+1

model.” For a two - no de cluster, there are now three proﬁles: the two local proﬁles ( N )

andaclustered proﬁle (+1). The clustered proﬁle canmovearoundthe cluster, andwhen

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 proﬁle (the “+1” proﬁle) is the active

node and all other nodes are passive (that is, running with their local “N” proﬁles).

On thePolyServe Management Console, theactivenodeisspeciﬁed as the primary

node and the passive nodes are speciﬁed as backup nodes.

Prerequisites

HP PolyServe Matrix Server 3.6.1

Installation instructions

See the HP Poly Serve M atrix Server Installation Guide for installation information. For

upgr

ades to 3.6.1 from an earlier release, see the HP PolyServe Matrix Server Upgrade

Guide