3.1.2 Matrix Server Upgrade Guide
Chapter 4: Double Upgrade Procedures 31
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
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.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.
• If you are using MxFS-Linux, you will need to perform an extra step to
unmount PSFS filesystems. See “Unmount Filesystems on Clusters
With MxFS-Linux” on page 50 for details.
Matrix Server 3.1.x Without MxFS-Linux
This procedure should be used only if you are running 3.1.x on a 32-bit
operating system and want to move to 3.1.2 on a 64-bit operating system.
The procedure is a double upgrade. The first upgrade installs Matrix
Server 3.1.2 on the 32-bit operating system. When all servers are running
Matrix Server 3.1.2, 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.
Complete the following steps to perform the upgrade.
NOTE: Upgrade the server with the highest IP address first. Then
continue to upgrade the servers in descending order of IP address,
with the lowest numbered server being upgraded last.
1. Back up the Matrix Server configuration as described under “Back Up
the Existing Matrix” on page 2.
2. Stop Matrix Server on the server:
# /etc/init.d/pmxs stop
3. If the following Matrix Server configuration files have been modified
at your site, save copies of the files. After the second installation of
Matrix Server, you can merge your local changes into the new versions
of the files.