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

Chapter 2: Overview 10

The tool must be installed on each node in the matrix, but is run from

only one node. The node does not need to be configured for the Virtual

SQL Servers being upgraded.

2. Run the Upgrade Tool

The upgrade tool attempts to fix any duplicate registry entries for the

specified Virtual SQL Server and the associated Virtual SQL instances

and then creates a new local profile for the primary node. Before running

the tool, ensure that the following requirements are met:

• Each Virtual SQL Server must be active on its primary node.

• Each Virtual SQL Server must have a backup that is enabled.

• If the cluster nodes configured for Virtual SQL Servers are using any

form of proxy server, add each node, or the subnet in which the node

is configured, to the proxy exclusion list on each node. This

configuration ensures proper communication among all nodes via

http while using the upgrade tool and can be backed out after the

upgrade is successfully completed.

For each Virtual SQL Server, run the following command from only one

node. Any node in the cluster can be used; the node does not need to be

associated with the Virtual SQL Server.

cscript /nologo mssql_upgrade.js /upgrade /vsql <vsql_name>

/backup <backup_IP> /path <path_target> /matrix <hostname>

/user <username> /password <password>

The options are:

/vsql <vsql_name>

The name of a Virtual SQL Server.

/backup <backup_IP>

The IP address of a valid backup node for the Virtual SQL Server. This

node will be used to copy the SQL data and recreate a local registry for

the primary node.

/path <path_target>

Where the upgrade tool should place the local “N” profile that it

creates for the primary node. The path_target should be a new