3.6.0 Matrix Server Upgrade Guide (5697-7085, February 2008)

Chapter 2: Overview 9

As an example of an upgrade, consider a Virtual SQL Server running on

two nodes in a 3.4 cluster. Node1 is the primary and active node. Node2 is

the backup and passive node. When the upgrade tool is invoked, it carries

out the following procedure:

1. Scans the registry on both Node1 and Node2 to check for duplicate

SQL registry values. Any duplicate values are fixed.

2. Copies the SQL data from Node2 to the specified path on a PSFS

filesystem, which will be used to store the local data for Node1.

3. Creates a local SQL registry referencing the local data for Node1.

4. Deposits a 3.6 reference count registry flag in Node1’s registry to

ensure that the 3.6 SQL engine can correctly utilize the local profile for

Node1 after the cluster is upgraded to 3.6.

Again, running the upgrade tool does not change or affect the running

behavior of MxDB for SQL Server 3.4. The tool simply prepares the

cluster for the upgrade by creating the local profile for the primary node.

Perform the Upgrade

The upgrade procedure includes the following steps:

1. Install the upgrade tool on all nodes in the cluster.

2. Run the upgrade tool on each Virtual SQL Server configured in the

cluster. The tool needs to be run from only one node in the cluster.

3. Uninstall the upgrade tool from all nodes in the cluster.

1. Install the Upgrade Tool

The MxDB for SQL Server 3.6 distribution includes the upgrade tool in

the following file:

MxUpgrade_SQL_3.6.0.<xxxx>.<arch>.msi

Copy this file to each node in the matrix and then double-click on the file

to install the tool. The installation places the tool, a Java script named

mssql_upgrade.js, in the following directory on the installation drive, C:

in the following example.

C:\Program Files\PolyServe\MatrixServer\bin