PolyServe® Matrix Server Upgrade Guide PolyServe® Matrix Server 3.4.0 for Windows Matrix Database Solution Pack for SQL Server 3.4.2 Matrix File Serving Solution Pack for CIFS 3.4.
Copyright © 2004-2006 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents 1 Overview Supported Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the Existing Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 2 2 Rolling Upgrades Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview Supported Upgrades Upgrades to Matrix Server 3.4.0 are supported from Matrix Server 3.2.1 or 2.7.2. If you are running a different version of Matrix Server, you will first need to upgrade to Matrix Server 2.7.2 or 3.2.1 and then upgrade to 3.4.0. Supported Operating Systems The supported operating systems for Matrix Server 3.4.
Chapter 1: Overview 2 • The \conf\debug subdirectory Do not back up the mounts and licenses subdirectories. You should also have recent backups of all PSFS filesystems for disaster recovery purposes. Upgrade Scenarios There are three ways to perform the upgrade to Matrix Server 3.4.0 and the corresponding version of the PolyServe Solution Packs: • Perform a rolling upgrade. In this procedure, servers are removed from the matrix, upgraded, and returned to the matrix one-at-a-time. No downtime is required.
2 Rolling Upgrades Overview This chapter describes how to perform a rolling upgrade of Matrix Server and the PolyServe Solution Packs. Upgrades are supported from Matrix Server 3.2.1 or 2.7.2. 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 3.4.
Chapter 2: Rolling Upgrades 4 order of IP address, with the server with the lowest primary IP address being upgraded last. • If a server is temporarily out of the matrix during the upgrade (for example, for maintenance), you will need to upgrade it to 3.4.0 before returning it to the matrix. • It is not necessary to upgrade the stand-alone Management Console, which is used to connect to the matrix from hosts not running the matrix software.
Chapter 2: Rolling Upgrades 5 DNS Requirement for Virtual SQL Servers MxDB for SQL Server 3.4.x requires that DNS be configured; using local host files is not supported. A DNS entry must exist for each Virtual SQL Server/IP address. The entry must include an A record and a [PTR] record for forward and reverse lookup. Windows authentication may fail if these records do not exist.
Chapter 2: Rolling Upgrades 6 servers. Do not change the state of virtual SQL Servers until all of the nodes have been upgraded to 3.4.0. • 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. • You will need to install a new license file during the upgrade.
Chapter 2: Rolling Upgrades 7 3. Back up the matrix configuration on the server as described under “Back Up the Existing Matrix” on page 1. 4. Shut down the server. 5. Install the new version of the operating system. 6. If you will be adding third-party MPIO software to the matrix, install it according to the product documentation. 7. Install a version of the HBA driver that is supported by Matrix Server.
Chapter 2: Rolling Upgrades 8 13. Install the PolyServe Solution Packs. – For MxDB for SQL Server, insert the Solution Pack CD into the CD drive or go to the location where you have downloaded the software. Then double click the file MxDB_SQL_3.4.x..msi and run the Installation Wizard. – For MxFS for CIFS, insert the Solution Pack CD into the CD drive or go to the location where you have downloaded the software. Then double-click the file MxFS_3.4.0..msi and run the Installation Wizard. 14.
Chapter 2: Rolling Upgrades 9 Upgrade Matrix Server Without Reinstalling the OS NOTE: If you are using MxDB for SQL Server, 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 3.4.0. Complete the following steps to upgrade the matrix to the 3.4.0 release. NOTE: Upgrade the server with the highest IP address first.
Chapter 2: Rolling Upgrades 10 5. Uninstall the following Matrix Server Solution Packs if they are installed on the server. MxFS for CIFS. Use the Control Panel Add/Remove Programs interface to do this. – Matrix Database Solution Pack for SQL Server – Matrix File Serving Solution Pack for CIFS 6. Uninstall Matrix Server. Use Start > Polyserve > MatrixServer > Uninstall Matrix Server. Select the checkbox to “Keep the existing MatrixServer configuration.
Chapter 2: Rolling Upgrades 11 Output from the utility appears on the screen and is also written to the Application Log section of the Event Viewer. We recommend that you fix any problems identified by mxcheck before you install Matrix Server. 13. Install Matrix Server 3.4.0. Locate the file MxS_3.4.0..msi on the product CD or in the directory where you downloaded the software. Double-click on the MxS_3.4.0..msi file and run the Installation Wizard.
Chapter 2: Rolling Upgrades 12 18. When asked if you want to start the Matrix Server service, answer yes. If you are not prompted to start the service, go to the Matrix Wide Configuration tab and start Matrix Server on the upgraded server. The upgraded server will now rejoin the matrix. Repeat this procedure on each remaining server in the matrix. If you are using MxDB for SQL Server, restore the Policy setting on each Virtual SQL Server to its original value after the upgrade is complete.
Chapter 2: Rolling Upgrades 13 Sparse files must be enabled on filesystems that will be used with MxDB for SQL Server. Caveat for Upgrades to Windows 2003 When upgrading the operating system to Windows 2003, you should be aware of the following: • If you are using TrendMicro, you may need to use the workaround described in the following TrendMicro Knowledge Base article: http://kb.trendmicro.com/solutions/solutionDetail.asp?solutionID=16836 Copyright © 1999-2006 PolyServe, Inc. All rights reserved.
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 Matrix Server 3.2.1 or 2.7.2.
Chapter 3: Non-Rolling Upgrades 15 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. • If a server is temporarily out of the matrix during the upgrade (for example, for maintenance), you will need to upgrade it to 3.4.
Chapter 3: Non-Rolling Upgrades 16 • A Virtual SQL 2005 instance cannot be a backup for a Virtual SQL 2000 instance having the same name (and vice versa). A Virtual SQL Instance and all of its backups must be running the same version of SQL Server. DNS Requirement for Virtual SQL Servers MxDB for SQL Server 3.4.x requires that DNS be configured; using local host files is not supported. A DNS entry must exist for each Virtual SQL Server/IP address.
Chapter 3: Non-Rolling Upgrades 17 a. Locate the Virtual SQL Instance on the PolyServe Management Console, right-click, and select Properties. b. On the Modify Virtual SQL Instance window, click the Advanced button. Then select the Scripts tab on the Advanced Service Configuration window. c. Remove the entries that you made for the Post Start and Pre Stop scripts. 2. Stop Matrix Server on the servers in group A.
Chapter 3: Non-Rolling Upgrades 18 Output from the utility appears on the screen and is also written to the Application Log section of the Event Viewer. We recommend that you fix any problems identified by mxcheck before you install Matrix Server. 11. On each server in group A, restore the Matrix Server configuration that you saved in step 3. Be sure to copy the \conf directory back to its original location: %Program Files%\PolyServe\MatrixServer\conf. 12.
Chapter 3: Non-Rolling Upgrades 19 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. Also check the HBA driver. 17. Go to the Matrix Wide Configuration tab and export the updated configuration to all other servers in group A. (You may be asked for the password on each server. Enter admin, which is the default password.
Chapter 3: Non-Rolling Upgrades 20 24. On each server in group B, install a supported HBA driver. 25. Reboot the servers in group B. 26. If the servers in group B use Emulex HBAs, install the HBA API libraries on each server. These libraries are provided with the HBAnyware package, which is included in the HBA driver download. 27. Run the PolyServe mxcheck utility on the servers. This utility verifies that the server’s configuration meets the requirements for running Matrix Server.
Chapter 3: Non-Rolling Upgrades 21 31. Start the PolyServe Management Console (if you are not already connected) and connect to one of the servers in group A (a server that has already been upgraded). Verify that all of the servers in group B have rebooted and then export the configuration from the group A server to the servers in group B. NOTE: If an export fails, verify that the FC switch ports are enabled for all of the servers.
Chapter 3: Non-Rolling Upgrades 22 c. Remove the entries that you made for the Post Start and Pre Stop scripts. 2. Stop Matrix Server on each server 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.) Also disable the MatrixServer service on the Microsoft Management Console Services snap-in. 3.
Chapter 3: Non-Rolling Upgrades 23 9. On each server in group A, upgrade HBA drivers if necessary. In particular, if you have upgraded to Windows 2003, you will probably need to install a new HBA driver. (For a list of supported HBA drivers, see the compatibility information on the PolyServe Web site.) 10. If necessary, reboot the servers in group A. (You will need to reboot the servers if this step is required by an operating system upgrade or if you installed a new HBA driver in step 9.) 11.
Chapter 3: Non-Rolling Upgrades 24 software. Then double click the file MxDB_SQL_3.4.x..msi and run the Installation Wizard. 15. Open the Matrix Server Connect window and enter the login credentials for a server in group A, but type admin for both the user and the password. Click the down arrow on the Connect button to see the options, and then click on Configure. (The upgrade does not retain your Administrator password; you will need to set it again in step 16.) 16. Install the new license file.
Chapter 3: Non-Rolling Upgrades 25 20. On the Matrix Wide Configuration tab, start Matrix Server on all of the servers in group A. NOTE: If you are not using the default matrix password, you will see a message stating that an attempt to login to the Management Console failed because of a bad password. You can ignore this message. Simply close the Configure Matrix window and then reconnect to the node using Start > Programs > PolyServe Matrix Server > Management Console.
Chapter 3: Non-Rolling Upgrades 26 26. If you will be adding third-party MPIO software to the matrix, install it on each server in group B according to the product documentation. 27. On each server in group B, upgrade HBA drivers if necessary. 28. If necessary, reboot the servers in group B. (You will need to reboot the servers if this step is required by an operating system upgrade or if you installed a new HBA driver in step 26.) 29.
Chapter 3: Non-Rolling Upgrades 27 software. Then double click the file MxDB_SQL_3.4.x..msi and run the Installation Wizard. 33. Start the PolyServe Management Console (if you are not already connected) and connect to one of the servers in group A (a server that has already been upgraded). Verify that all of the servers in group B have rebooted and then export the configuration from the group A server to the servers in group B.
Chapter 3: Non-Rolling Upgrades 28 The device can be specified in several ways: – By the drive letter, such as X: – By the mount point (junction), such as C:\san\vol2 – By the psd or psv name, such as psd2p2 or psv3 Sparse files must be enabled on filesystems that will be used with MxDB for SQL Server.
