HP StorageWorks HP PolyServe Software 4.1.0 upgrade guide This document describes how to upgrade to HP PolyServe Matrix Server 4.1.0, HP PolyServe Software for Microsoft SQL Server 4.1.0, and HP PolyServe Software for Windows File Serving 4.1.0.
Legal and notice information © Copyright 2004, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview ......................................................................... 4 Supported operating systems ................................................................................ Upgrade checklist ................................................................................................ Remove Virtual MSDTC configuration ..................................................................... Back up the existing matrix ...........................................................
1 Overview This document describes upgrades to the following products: • HP PolyServe Matrix Server 4.1.0. • HP PolyServe Software for Microsoft SQL Server 4.1.0. • HP PolyServe Software for Windows File Serving 4.1.0. Upgrades are supported only from the 3.6.x and 4.0.0 versions of these products. If you are running an earlier version, you will first need to upgrade to the 3.6.x releases and then upgrade to Matrix Server 4.1.0.
Action Description • Rolling upgrade with new OS Review “Upgrade considerations” on page 7 and then upgrade each server as described under “Rolling upgrade procedure” on page 9. • Non-rolling upgrade with new OS Review “Upgrade considerations” on page 14 and then upgrade the servers in groups or all at once. See “Non-rolling upgrade procedure” on page 15. Upgrade the HP PolyServe Management Console on clients. See Chapter 4 on page 21.
mpdump -f Back up the matrix configuration The Matrix Server service should not be running when you perform the backup. The default location for the matrix configuration files is %Program Files%\PolyServe\ MatrixServer\conf on the drive where you installed Matrix Server. Back up the following from the conf directory: • The files directly under \conf • The \conf\debug subdirectory Do not back up the mounts and licenses subdirectories.
2 Rolling upgrades Overview Rolling upgrades are supported from the Matrix Server, MxDB for SQL Server, and MxFS for CIFS 3.6.x and 4.0.0 releases. Custom installations of Matrix Server When you upgrade Matrix Server, the Installer looks for the matrix configuration files in the location where Matrix Server is currently installed and then applies the configuration files to the new installation. If you perform a custom installation of Matrix Server 4.1.
• • • • • • • cedure (such as installing a new license). Do not install the stand-alone Management 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.
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.
11. Install HP PolyServe Matrix Server 4.1.0. Locate the file MxS_4.1.0..msi on the product CD or in the directory where you downloaded the software. Right-click the MxS_4.1.0..msi file and select Run as Administrator to start the Installation Wizard. To complete the installation, reboot the server as directed by the popup message. 12. Run the mxcheck utility provided with Matrix Server 4.1.0. This utility verifies that the server’s configuration meets the requirements for running Matrix Server.
17. Click Apply (on the bottom of the Matrix Configuration window) to save the Matrix Server configuration. NOTE: If the Apply fails, verify that the FC switch ports are enabled for all of the servers. If the switch ports are enabled, check the Windows Disk Management MMC snap-in to determine whether the node can see the disks on the SAN and whether the disks are online. Also check the HBA driver. 18. When asked if you want to start the Matrix Server service, answer yes.
23. For each remaining server in the matrix, repeat this procedure through step 13. Next, open the Configure Matrix window (if it is not already open) and import the matrix configuration from a server running Matrix Server 4.1.0 to the server being upgraded (the new license is included in the imported configuration). You can then start the Matrix Server service on the newly upgraded server. 24.
3 Non-rolling upgrades Overview If you are not performing a rolling upgrade, you can use one of the following methods to upgrade the matrix: • 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. This method minimizes downtime. • Upgrade all servers at once. Upgrades are supported from the 3.6.x releases only.
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.1.0 version of the stand-alone PolyServe Management Console can be used during the upgrade to connect to servers running 3.6.
the state of virtual SQL Servers until all of the nodes have been upgraded to HP PolyServe Software for Microsoft SQL Server 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.
4. Stop Matrix Server on the servers in group A. (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 each server in group A as described under Back up the existing matrix, page 5. 6. Shut down the servers in group A. 7. Reinstall the operating system on the servers in group A. 8.
15. Open the Configure Matrix window. On the console for the server being upgraded, select Start > Programs > PolyServe Matrix Server > PolyServe Configuration Utility. Answer no if you are asked whether you want to start the matrix on the server and then select the configure option. If you are asked for login credentials, enter the credentials for the server that you are upgrading. Then click the down arrow on the Connect button to see the options and select Configure. 16. Install the new license file.
19. On the Matrix Wide Configuration tab, start Matrix Server on all of the servers in group A. The servers in group A are now operational. IMPORTANT: Be sure to review the drive letter and mount point assignments on each server and restore any missing or incorrect assignments. 20. If you are using HP PolyServe Software for Microsoft SQL Server, install the SQL instance on the newly upgraded server. On the PolyServe Management Console, select Tools > Install SQL.
32. Run the mxcheck utility on the servers. This utility verifies that the server’s configuration meets the requirements for running Matrix Server. To run mxcheck, insert the Matrix Server CD into the CD drive or go to the directory where you downloaded the product and then double-click the file mxcheck.exe. Output from the utility appears on the screen and is also written to the Application Log section of the Event Viewer.
37. Apply SQL Server service pack/hot fixes on the upgraded servers. On the PolyServe Management Console, select Tools > SP/Hotfix Update SQL. Select only the newly upgraded servers for installation. 38. Reboot the upgraded servers. 39. Enable hosting on the upgraded servers. On the Management Console, open the Virtual Hosts tab and select the virtual host (such as a Virtual SQL Server or Virtual CIFS Server) that was primary on that server. Right-click and select Rehost.
4 Upgrade the HP PolyServe Management Console on clients The stand-alone HP PolyServe Management Console must be upgraded to version 4.1.0 on any client systems currently running an earlier version of the console. The stand-alone console cannot be installed on a server running Matrix Server 4.1.0. (Matrix Server includes a built-in version of the HP PolyServe Management Console.) Complete these steps: 1. Remove the old version of the console using Add/Remove Programs on the Control Panel. 2.
Upgrade the HP PolyServe Management Console on clients
A Support and other resources HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
