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

of virtual SQL Servers until all of the nodes have been upgraded to HP PolyServe
Software for Microsoft SQL Server 4.0.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.
Non-rolling upgrade procedure
To minimize overall downtime, divide your servers into two groups and then upgrade
one group at a time while the other group runs the matrix. The upgrade procedure
assumes that the servers are divided into group A and group B.
If you prefer to upgrade all servers at once instead of in groups, be sure to take the
following steps to retain the matrix configuration:
• Leave one server running the old operating system and matrix software. You can
shut down the other servers as indicated below.
• After the first server is upgraded to the new operating system and matrix software,
export the matrix configuration from a server running 3.6.x to this server..
• Upgrade all remaining servers, including the server running the older software,
and export the matrix configuration to them (as in step 17).
To perform the upgrade, complete the following steps.
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. 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 to
the 4.0.0 release.
3. If the node to be upgraded is primary for any application, rehost the application
to another node.
HP PolyServe Software upgrade guide 15