3.4.0 Matrix Server Upgrade Guide

Chapter 2: Rolling Upgrades 4

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.4.0 before

returning it to the matrix.

• It is not necessary to upgrade the stand-alone Management Console,

which is used to connect to the matrix from hosts not running the

matrix software. When you use the stand-alone Management Console

to connect to a matrix running version 3.4.0, the latest version of the

Management Console will be downloaded to the host.

• 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 for HP Secure Path Users

If you are upgrading from Matrix Server 2.7.2, we recommend that you

migrate HP StorageWorks Secure Path to DSM. Before making this

change, be sure to consult with HP regarding their storage support for

HP DSM.

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.