File Locations: ftp://cdburn-win.smq.datapipe.net/home/software/3par/SQL/Upgrade/3ParUpgradePackage.zip Goal: Compare installed version of each product to the latest required version. All required versions are listed at the top of the sheet, the installed versions are in line. If the installed version is older than the required version, than update it. The only way to ignore a patch is for Win 2008 Server that do NOT use Recovery Manager, these you can skip the VSS Patch. This is the only exception. Only one reboot should be required. Overview of Patches, with required versions. Install instructions below. ==================================== Windows 2003 SP2 Versions -- 3Par VSS Version - 1.6.2.X -- This is 3Par's VSS Software 3Par RMSQL Version - 3.0.2, Patch 02 -- This is 3Par's Recovery Manager Software MPIO Version - 1.23.X -- This is 3Par's MPIO software Storport Hotfix - 5.2.3790.4189 -- This is a Microsoft Hot Fix (http://support.microsoft.com/kb/945119) VSS Rollup - 5.2.3790.4143 -- This is a Microsoft VSS Rollup (http://support.microsoft.com/kb/940349) Windows 2008 SP2 Versions -- 3Par VSS Version - 1.6.2.X -- This is 3Par's VSS Software 3Par RMSQL Version - 3.0.2, Patch 02 -- This is 3Par's Recovery Manager Software VSS Hotfix - 6.0.6002.22137 -- This is a Microsoft Hotfix (http://support.microsoft.com/kb/970770) ===================================================== **** Skip the steps that are N/A for your upgrade process. Not all steps are needed for every install. **** Step 1 Download the necessary installers from CDburn and Microsoft site. There is a zip file on CD Burn that has all needed 3Par installers and Microsoft Hotfix, located here: ftp://cdburn-win.smq.datapipe.net/home/software/3par/SQL/Upgrade/3ParUpgradePackage.zip Step 2 Do management servers (DC's) last. Do inactive Cluster nodes first. Step 3 (Windows 2003 ONLY) Have backups remove all Brocade Paths to all LUNS BUT one path. One path must remain Step 4 Stop 3par VSS service if it is running Stop Recovery Manager Service Step 5 If a Cluster, you must make sure MSDTC is active on the node your working on. If not failover MSDTC Group only. A) Uninstall 3PAR Recover Manager for SQL from add/remove B) Uninstall 3PAR VSS provider from add/remove Step 6 Log Off the server and than log back on Step 7 Install VSS (1.6.2), make sure you pick the correct OS and architecture (e.g., for Win 2003 X 64 use setup_2k3_x64.exe). Make sure you have the login info for 3 Par and check SSL box. (It may required to install .NET 3.5 prior to the VSS upgrade, the .NET 3.5 installer is located in its sub-directory) Step 8 Log Off the server and than log back on Step 9 Install Recovery Manager 3.02 and Patch 02. Make sure you use the correct OS and architecture. A) If the DC/Management server choose the option -- Recovery Manager Backup Server for DC B) If the SQL Servers choose the option -- Recovery manager Agent for SQL instances C) Recovery Manager 3.0.2 Patch 02 -- pick repair option and do not reboot. *** NOTE: The only way to know if Patch02 is installed is to check add/remove. Just because the spreadsheet shows 3.02 as the installed version of Recovery Manager, it still may need the patch. Step 10 Install any applicable Hot Fixes, but do not reboot. Make sure you check the box at the end of the install to NOT REBOOT Step 11 (ONLY if MPIO is version 1.17 and windows 2003 X64, else SKIP this step) Within the install directory for MPIO there is a folder: .\patch\x64. Run mmp1017.exe from that command line. Do not just double click Step 12 Install MPIO (1.0.23) from .\%ArchitectureType%\MSMPIO.msi and reboot Step 13 have backups enable all paths Step 14 If Recovery Manager was upgraded, test a SnapShot