3.1.2 Matrix Server Upgrade Guide

Chapter 3: Single Upgrade Procedures 13

• During the rolling upgrade, the matrix will include a mix of servers

running 3.1.2 and the earlier release (2.7/3.x). As long as the matrix

includes at least one active server running 2.7/3.x, other servers

running that version will be able to join the matrix (for example,

following a reboot). However, after the last server running 2.7/3.x has

left the matrix, only servers running 3.1.2 can join the matrix.

Although Matrix Server supports a mix of servers running 3.1.2 and

2.7/3.x during the rolling upgrade, on-going operation of a mixed-

version cluster is not supported. All servers should be upgraded to

3.1.2 as quickly as possible.

• During the upgrade, a mix of servers running 3.1.2 and 2.7/3.x may

have a PSFS filesystem mounted. After the PSFS filesystem has been

unmounted on the last node running 2.7/3.x, the filesystem cannot be

mounted on a 2.7/3.x node unless it is first unmounted on the nodes

running 3.1.2.

• For best results while the matrix includes a mix of 3.1.2 and 2.7/3.x

servers, all UI operations (either via the Management Console or the

mx command-line utility) should be connected to a 2.7/3.x server.

• During the rolling upgrade, filesystems cannot be upgraded to add

new features such as filesystem quotas. Instead, you will need to

complete the rolling upgrade first. Then unmount the filesystems

either one-at-a-time or, for MxFS-Linux, one export group at a time

and perform the filesystem upgrade.

• Before performing the upgrade, you will need to obtain a new license

file from your MatrixLink account. You can install the license file

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.1.2. If you

want to change any of the parameters that you originally specified

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

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

stop), and then rerun mxconfig.