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

Chapter 4: Non-Rolling Upgrades 25

• If you need to install the 3.6.0 release in a different location, copy the

backup configuration files (see “Back Up the Existing Matrix” on page

6) to that location before installing Matrix Server 3.6.0.

Upgrade Considerations

When upgrading Matrix Server, you should be aware of the following:

• 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.

• It is important to upgrade all nodes in the matrix within a short time

frame. We do not recommend running the matrix for an extended

period of time with only some of the nodes upgraded to 3.6.0. This

release introduces a new configuration data repository and a new

logging facility that do not become fully functional until all nodes are

upgraded. If the matrix is only partially upgraded, alerts raised by

nodes running 3.6 will be improperly logged by nodes running 3.4.

Also, until the entire matrix is upgraded, many services that are run

on 3.6 nodes must be run as local system administrator.

• 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 versions of Matrix

Server and any PolyServe Solution PacksMxFS for CIFS.

Upgrade Considerations for MxDB for SQL Server

All existing Virtual SQL Servers and the associated Virtual SQL instances

must be upgraded before the Matrix Server 3.6 upgrade. See “The MxDB

for SQL Server Upgrade Tool” on page 7 for more information.