4.0.0 HP Polyserve Matrix Server Upgrade Guide (T5392-96049, April 2010)

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.
• The 4.0.0 version of the stand-alone PolyServe Management Console can be
used during the upgrade to connect to servers running 3.6. However, there can
be a long delay when opening the console on a server running 3.6. The console
should be used only to view the cluster status; do not make configuration changes
other than those specified in the upgrade procedure (such as installing a new li-
cense). Do not install the stand-alone Management Console on a server in the
matrix as it can conflict with the console that is installed with Matrix Server.
• If a server is temporarily out of the matrix during the upgrade (for example, for
maintenance), you will need to upgrade it to 4.0.0 before returning it to the
matrix.
• If you are upgrading to the 64-bit operating system, be sure to install the 64-bit
version of the HBA driver.
• During the upgrade, the PolyServe Management Console will show the version
of Matrix Server that is currently running on the server to which you are connected.
Each server will show the currently installed version of the operating system.
• 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 4.0.0 version.
• It is important to record the existing drive letter and mount point assignments before
upgrading each server. Because of the behavior of the Windows 2008 mount
manager, it is possible that some of the drive letter or mount point assignments
will be missing or assigned incorrectly after the upgrade and will need to be
manually restored.
• In Windows 2008, the SAN storage is kept offline by default, as the SAN policy
is set to “Offline Shared.” Use the command-based diskpart utility or the GUI-
based Windows Disk Management utility to bring the storage online for the first
node being configured. If the diskpart utility is used, you will need to clear the
read-only disk attributes after the storage is online.
Upgrade considerations for MxDB for SQL Server
These considerations apply to sites running MxDB for SQL Server:
• Maintenance operations performed via MxDB for SQL Server are not supported
while the matrix includes a mix of 4.0.0 and 3.6 servers. Do not change the state
Non-rolling upgrades14