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

cedure (such as installing a new license). Do not install the stand-alone Manage-
ment Console on a 4.1.0 server as it can conflict with the console that is installed
with Matrix Server.
• You will need to install a new 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.
• If a server is temporarily out of the matrix during the upgrade (for example, for
maintenance), you will need to upgrade it to 4.1.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.1.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.1.0 and 3.6.x/4.0.0 servers. Do not change
the state of virtual SQL Servers until all of the nodes have been upgraded to 4.1.0.
For SQL Server 2005, SP2 is required if you will be using FTE. SP2 provides the
NTLM Security Support Provider (NTLMSSP) service, which is used by FTE. Because
Windows Server 2008 does not include the NTLMSSP service, FTE will fail if SP2
is not installed.
Rolling upgrades8