4.1.0 HP Polyserve Matrix Server Upgrade Guide (T5392-96067, October 2010)

Rolling upgrade procedure
The rolling upgrade procedure does not require matrix downtime, but clients may
experience brief outages during failovers. Each server is removed from the matrix,
upgraded, and then returned to the matrix.
Complete the following steps to upgrade the matrix to the 4.1.0 release.
NOTE:
Upgrade the server with the highest IP address 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.
1. Record the existing drive letter and mount point assignments on the 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.
2. If MxDB for SQL Server is installed, set the Policy on each Virtual SQL Server to
AUTOFAILBACK before you begin the upgrade. This step ensures that the Virtual
SQL Servers will start on their primary nodes after the nodes are upgraded.
3. If the node to be upgraded is primary for any application, rehost the application
to another node.
4. Stop Matrix Server on the server to be upgraded. (Either issue the command
net stop matrixserver from the Command Prompt, or stop the product
via the Microsoft Management Console Services snap-in.)
5. Back up the matrix configuration on the server as described under “Back up the
existing matrix” on page 5.
6. Shut down the server.
7. Install the new version of the operating system.
8. If you will be adding third-party MPIO software to the matrix, install it according
to the product documentation.
9. Install a version of the HBA driver that is supported by Matrix Server.
10. Reboot the server.
HP PolyServe Software 4.1.0 upgrade guide 9