3.5.1 Matrix Server Upgrade Guide

Chapter 3: Double Rolling Upgrades 23

mixed-version cluster is not supported. All servers should be

upgraded to 3.5.1 as quickly as possible.

• During the upgrade, a mix of servers running 3.5.1 and the older

release may have a PSFS filesystem mounted. After the PSFS

filesystem has been unmounted on the last node running the older

release, the filesystem cannot be mounted on a node running the older

release unless it is first unmounted on the nodes running 3.5.1.

• For best results while the matrix includes a mix of servers running

3.5.1 and the older release, all UI operations (either via the

Management Console or the mx command-line utility) should be

connected to a server running the older release.

• Before performing an upgrade from 3.1.2, you will need to obtain a

new license file from your MatrixLink account. The new license file

can be installed during the upgrade. If the new file is not in place

when you start Matrix Server, license violations will be reported on

the Management Console and in the matrix log, and the product will

shut down after one hour and 45 minutes.

• You do not need to run mxconfig when upgrading to 3.5.1. If you

want to change any of the parameters that you originally specified

with mxconfig, first upgrade all servers to 3.5.1. After the upgrade is

complete, stop Matrix Server on each server (use /etc/init.d/pmxs

stop), and then rerun mxconfig.

Double Upgrade with MxFS-Linux

This procedure should be used only if you are running Matrix Server and

MxFS-Linux 3.1.2 on a 32-bit operating system and want to move to

Matrix Server and MxFS-Linux 3.5.1 on a 64-bit operating system. The

procedure is a double upgrade. The first upgrade installs Matrix Server

3.5.1 on the 32-bit operating system. When all servers are running Matrix

Server 3.5.1, the second upgrade is done to take the operating system to

64-bit mode. Matrix Server must then be reinstalled to take advantage of

64-bit mode.