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

Chapter 3: Rolling Upgrades 16

• The server with the numerically highest primary IP address must be

upgraded first. Then continue to upgrade the servers in descending

order of IP address, with the server with the lowest primary IP

address being upgraded last.

• If a server is temporarily out of the matrix during the upgrade (for

example, for maintenance), you will need to upgrade it to 3.6.0 before

returning it to the matrix.

• The stand-alone Management Console, which is used to connect to

the matrix from hosts not running the matrix software, must be

upgraded to the 3.6.0 version.

• If you are upgrading to the 64-bit operating system, be sure to install

the 64-bit version of the HBA driver and the 64-bit version of Matrix

Server and any PolyServe Solution Packs.

Upgrade Considerations for MxDB for SQL Server

All existing Virtual SQL Servers and the associated Virtual SQL instances

must be upgraded before starting the rolling upgrade to Matrix Server

3.6. See “The MxDB for SQL Server Upgrade Tool” on page 7 for more

information.

Upgrade Considerations for SQL Server 2005

If you will be upgrading SQL Server 2000 instances to SQL Server 2005,

you should be aware of the following:

• Before upgrading a SQL Server 2000 instance, remove the

corresponding Virtual SQL Instance from the Virtual SQL Server. (On

the PolyServe Management Console, right-click on the Virtual SQL

Instance and select Delete.) After the instance is upgraded, you can

recreate the Virtual SQL Instance.

• A Virtual SQL 2005 instance cannot be a backup for a Virtual SQL 2000

instance having the same name (and vice versa). A Virtual SQL

Instance and all of its backups must be running the same version of

SQL Server.