3.5.1 Matrix Server Upgrade Guide

Chapter 1: Overview 5

To restore the Export Group configuration, copy the saved dump file to a

directory in the Matrix Server directory structure. Then run the following

command in that directory.

$ mx --continue --file dump_<exportgroupname>_<time_in_milliseconds>

NLM State

You should also save the state of the Network Lock Manager (NLM),

which will be either enabled or disabled.

Run the following command to determine the state:

/opt/polyserve/bin/mxnlmconfig -q

This command returns a sentence stating whether NLM locking is

enabled or disabled. Be sure to save this information.

To restore the NLM state, run the mxnlmconfig command, using the -e

option to enable NLM locking, or the -d option to disable NLM locking.

/opt/polyserve/bin/mxnlmconfig [-e|-d]

Back Up PSFS Filesystems

You should also back up all PSFS filesystems. If you are using quotas, also

run the Matrix Server psfsdq command to back up the quota information

stored on the filesystems. You will not need these backups during a

normal upgrade, but it is important to have them for disaster recovery

purposes.

Supported Upgrade Procedures

The following methods can be used to upgrade to the 3.5.1 release:

• Single rolling upgrade. In this procedure, each server is removed

from the matrix, upgraded, and then returned to the matrix. No

matrix downtime is required. The operating system architecture

(either 32-bit or 64-bit) cannot be changed during the upgrade. See

Chapter 2.

• Double rolling upgrade. This method is for sites that are moving

from a 32-bit operating system to a 64-bit operating system. Each