VERITAS SANPoint Foundation Suite 3.4 patch03 upgrade procedure and component matrix

Article:TECH19610  |  Created: 2004-01-21  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH19610
Article Type
Technical Solution


Environment

Issue



VERITAS SANPoint Foundation Suite 3.4 patch03 upgrade procedure and component matrix

Solution



This TechNote describes the procedure for upgrading from previous releases of VERITAS SANPoint Foundation Suite (SPFS) (Cluster File System) to SPFS 3.4 Patch 03. This document is in two sections. The first section describes upgrading to SPFS 3.4 Patch03 from earlier SPFS releases. The second section lists the component products that comprise the various SPFS releases. Use the information in the second section to verify whether the installation of SPFS is at the correct patch level. SPFS 3.4 update2 and SPFS 3.4 patch02 are the same. Here SPFS 3.4 update2 will be referred to as SPFS 3.4 patch02.

Section I:

If you have systems that are at the SPFS 3.4 patch02 level, follow the procedure in part A to upgrade to SPFS 3.4 patch03.

If your systems are at levels previous to 3.4 patch02, first complete the procedure given in part B to upgrade to 3.4 Patch02. After you have upgraded all systems to 3.4 patch02, follow the procedure in part A to upgrade to SPFS 3.4 patch03.

A) SPFS upgrade from 3.4 patch 02 to 3.4 patch 03:

Note: You cannot upgrade directly to 3.4 Patch 03 from CFS 3.4 or CFS 3.4 Patch 01.

1. Log in as superuser.

2. From any node in the cluster, make the VERITAS Cluster Server (VCS) configuration writable:

# haconf -makerw

3. Select another node (in this example, node1) and stop VCS:

# hasys -freeze -persistent -evacuate node1

This also unmounts all cluster mounted file systems in the VCS configuration and stops VERITAS Cluster Volume Manager (CVM).

4. Write the VCS configuration to disk:

# haconf -dump -makero

5. Move to the patches directory in the downloaded SPFS 3.4patch03 directory:

# cd <your_download_path>/SPFS_3.4PATCH03/patches

6. Add the required patches:

# patchadd -M . 110435-07 110436-03 111909-04 111904-04

7. Remove VRTSlic package on the node. Remove the package even if a warning, indicating other packages are dependent, displays.

# pkgrm VRTSlic

8. Move to the pkgs directory:

# cd <your_download_path>/SPFS_3.4PATCH03/pkgs

9. Add the new VRTSlic package

# pkgadd -d . VRTSlic

10. Reboot the node.

11. Make the VCS configuration writable and restart VCS:

# haconf -makerw
# hasys -unfreeze -persistent node1

12. Write the VCS configuration to disk:

# haconf -dump -makero

13. Bring the CVM group and any other resources online:

# hagrp -online cvm -sys node1

Online any other resources.

Perform the above procedure on every node in the cluster.


B) To upgrade from earlier releases to 3.4 Patch 02:


This section describes how to perform an online upgrade on a multi-node VERITAS Cluster File System (CFS). Follow this procedure if you have a cluster installed prior to SPFS 3.4 patch02. After completing this upgrade, use the steps provided in part A to upgrade to SPFS 3.4 patch03 level.

See the VERITAS SANPoint Foundation Suite HA 3.4 Release Notes for information on the release levels of the CFS software components that can be upgraded. Use one of the VCS GUIs to begin removing CFS resources, or use the command-line procedures below.

Note: CFS (SPFS) operates only on Solaris 8 (32-bit and 64-bit) operating systems.For Cluster File System functionality to work reliably on Solaris 8, you must have Sun patch ID 110383-01, 108528-02, 108901-03, 109529-06, and 111413-02 (requires SUNWsan package) or later versions of these patches installed.

1. Log in as superuser.

2. From any node in the cluster, make the VCS configuration writable:

# haconf -makerw

3. Select another node (in this example, node1) and enter the following command to stop VCS:

# hasys -freeze -persistent -evacuate node1

This also unmounts all cluster mounted file systems in the VCS configuration and stops CVM.

4. Remove all VERITAS software packages on the node except VRTSvcs, VRTSperl, and VRTSvxvm (including optional packages for documentation and VRTScscm):

# pkgrm VRTScavf VRTSvxfs VRTScfsdc VRTSvmdev VRTSvmsa VRTSvmdoc \
VRTSvcsdc VRTSvmman VRTSglm VRTSlic VRTSgab VRTSllt VRTScscm

5. Reboot the node.

6. Place the VERITAS Software CD into a CD-ROM drive and move to the /cdrom directory:

# cd /cdrom/CD_name/pkgs

Note: To upgrade a system with the root disk encapsulated, add all packages below except VRTSvxvm. For information on upgrading VxVM with the root disk encapsulated, refer to the Volume Manager Installation Guide (igbook.pdf) available in the VRTSvmdoc package. Specifically the section "Upgrading VxVM on an Encapsulated Root Disk."

7. Add all the new packages except VRTSvcs and VRTSperl (documentation packages and VRTScscm are optional):

# pkgadd -d . VRTSlic VRTSvxfs VRTSvxvm VRTSvmdev VRTSvmsa \
VRTScavf VRTSglm VRTSvmdoc VRTSvmman VRTScfsdc VRTSvcsdc \
VRTSllt VRTSgab VRTSvcsw VRTSweb VRTScscm

8. Move to the patches directory:

# cd /cdrom/CD_name/patches

9. Add the required patches:

# patchadd -M . 110435-05 110436-02 111897-01

10. Reboot the node.

11. Restart VCS:

# hasys -unfreeze -persistent node1

12. Bring the CVM group online:

# hagrp -online cvm -sys node1

Perform the above procedure on every node. After all the packages are upgraded on all the nodes, you can begin to upgrade to the new VCS package. Up to this point, the cluster maintained its monitoring and failover capability. As you replace VCS, there is a short window of time when monitoring and failover capability cannot function. See the VERITAS Cluster Server Installation Guide for detailed information on upgrading VCS.

1. The types.cf file installed with VCS 2.0 contains new type definitions. If your current configuration altered the default types.cf file originally installed on your cluster, make a copy of it for use later:

# cp /etc/VRTSvcs/conf/config/types.cf \
/etc/VRTSvcs/conf/types.save

2. The new VCS configuration file, /etc/VRTSvcs/conf/config/main.cf, is not compatible with the previous version. Make a copy of the current main.cf configuration file to edit after VCS 2.0 is installed:

# cp /etc/VRTSvcs/conf/config/main.cf \
/etc/VRTSvcs/conf/config/main.save

3. To begin upgrading VCS, write the VCS configuration to disk:

# haconf -dump -makero

4. Remove the configuration file to allow a new configuration to be installed:

# rm /etc/VRTSvcs/conf/config/main.cf

5. Stop VCS on all nodes:

# hastop -all -force

At this point, applications may still be running, but they are not being monitored by VCS.

6. Remove VRTSvcs and VRTSperl:

# pkgrm VRTSvcs VRTSperl

7. If the VERITAS Software CD is no longer in place, insert it into a CD-ROM drive and move to the /cdrom directory:

# cd /cdrom/CD_name/pkgs

8. Add the new VRTSvcs and VRTSperl packages:

# pkgadd -d . VRTSvcs VRTSperl

9. Compare the saved types.cf file (created in step 1 above) to the newly installed /etc/VRTSvcs/conf/config/types.cf:

# diff -w /etc/VRTSvcs/conf/types.save \
/etc/VRTSvcs/conf/config/types.cf

If the differences include any types defined in the types.save file, edit the newly installed /etc/VRTSvcs/conf/config/types.cf file, adding the types used in your previous configuration.

10. You must run the script upgradecfg.pl to remove obsolete attributes from the main.cf file. First, set the variable VCS_HOME. If you are using the Bourne Shell (sh or ksh), type:

# VCS_HOME=/opt/VRTSvcs; export VCS_HOME

If you are using the C Shell (csh), type:

% setenv VCS_HOME /opt/VRTSvcs

11. The upgradecfg.pl command uses the following syntax:

./upgradecfg.pl -i file_to_convert -o new_file_name

(You can print the usage for the command by entering the -h option.) Run the upgradecfg.pl command to remove the old attributes:

# ./upgradecfg.pl -i /etc/VRTSvcs/conf/config/main.save \
-o /etc/VRTSvcs/conf/config/main.cf

12. In the main.cf file, after the UserNames attribute, add the line that includes those users who are to function as administrators. For example:

UserNames = { admin = "cDRpdxPmHpzS.", joe = "eorDRerxPrzPx" }
Administrators = { admin }

Note: You can repeat step 9, step 10, step 11, and step 12 above on each node or simply copy main.cf and types.cf to all the other nodes.

13. Run the licensing utility on each node so that you can enter a license key (see "Obtaining a License Key" on page xii if you do not have a valid license key):

# ./licensevcs

14. Enter the license key as shown in the following example: Enter the license key for node1: 9999-9999-9999-9999-9999-999

15. Start VCS on each node:

# hastart

At this point, the VCS monitoring and failover capability is fully functional.


Section II:

The following tables show all the components of CFS/SPFS for various patch versions of CFS( 3.4 patch01, 3.4 patch02, 3.4 patch03 etc., ).The following are the set of components which officially constitute the various patch releases.

1. 3.4 patch 03:

The following are the list of components that officially form SPFS 3.4 patch03.

Packages and patchespkginfo -l (package name)pkginfo -l (package name)Requirements
Component(s) of CFSVERSION STRINGTIME STAMPREQUIRED patch(es) before upgrade
VRTScavf2.0,REV=BUILD1VERITAS-2.0agents-2001-07-24N/A
VRTSvxfs3.4,REV=GA032000-11-21N/A
VRTSglm3.4,REV=GA022000-11-20N/A
VRTScfsdc3.4,REV=PATCH02_BUILD4d2001-08-13N/A
VRTSvcs2.02001080900N/A
VRTSllt2.008/09/01-02:52:31N/A
VRTSgab2.02001080900N/A
VRTSperl2.0m0901N/A
VRTSvcsdc2.02001.08.15-17.25.38N/A
VRTScscm2.0(JDK1.3)2001080902N/A
VRTSvcsw2.02001080901N/A
VRTSweb1.1.12001080901N/A
VRTSlic1.0.1,REV=10.22.2001.19.501.0-2049.0N/A
VRTSspt1.2,REV=02.21.2002.16.4621-Feb-2002N/A
VRTSvmdev3.2,REV=08.15.2001.23.2914-AUG-2001N/A
VRTSvmman3.2,REV=08.15.2001.23.2714-AUG-2001N/A
VRTSvmsa3.2,REV=07.27.2001.19.47July 27,2001N/A
VRTSvxvm3.2,REV=08.15.2001.23.2714-AUG-2001SUNWsan, 109529-06, 111413-02
   MPXIO:110912-01, 111412-02
VRTSvmdoc3.2,REV=08.21.2001.16.0414-AUG-2001N/A
patch 110435-073.2,REV=08.21.2001.16.042002_03_12110383-01, 108528-02, 108901-03
patch 110436-033.4,REV=PATCH03_BUILD22002_02_07110435-07
patch 111904-04VERITAS-3.2t_p1.627-November-2001N/A
patch 111909-04VERITAS-3.2t_p1.621-November-2001N/A


2. 3.4 patch 02

The following are the list of components that officially form SPFS 3.4 patch02.

Packages and patchespkginfo -l (package name)pkginfo -l (package name)Requirments
Component(s) of CFSVERSION STRINGTIME STAMPREQUIRED patch(es) before upgrade
VRTScavf2.0,REV=BUILD1VERITAS-2.0agents-2001-07-24N/A
VRTSvxfs3.4,REV=GA032000-11-21N/A
VRTSglm3.4,REV=GA022000-11-20N/A
VRTScfsdc3.4,REV=PATCH02_BUILD4d2--1-08-13N/A
VRTSvcs2.02001080900N/A
VRTSllt2.008/09/01-02:52:31N/A
VRTSgab2.02001080900N/A
VRTSperl2.0m0901N/A
VRTSvcsdc2.02001.08.15-17.25.38N/A
VRTScscm2.0(JDK1.3)2001080902N/A
VRTSvcsw2.02001080901N/A
VRTSweb1.1.12001080901N/A
VRTSlic1.0.1,REV=08.15.2001.22.011.0-2049.0N/A
VRTSspt1.009-Aug-2001N/A
VRTSvmdev3.2,REV=08.15.2001.23.2914-AUG-2001N/A
VRTSvmman3.2,REV=08.15.2001.23.2714-AUG-2001N/A
VRTSvmsa3.2,REV=07.27.2001.19.47July 27,2001N/A
VRTSvxvm3.2,REV08.15.2001.23.2714_AUG_2001SUNWsan, 109529-06, 111413-02
   MPXIO:1110912-01, 111412-02
VRTSvmdoc3.2,REV=08.21.2001.16.0414-AUG-2001N/A
patch 110435-053.4,REV=PATCH02_BUILD4d2001_07_20110383-01, 108528-02, 108901-03
patch 110436-023.4,REV=PATCH02_BUILD4d2001_08_24110435-05
patch 11897-01VERITAS-3.2t_spfs28-August-2001N/A


3. 3.4 Patch 01

The following are the list of components that officially form SPFS 3.4 patch01.

Packages and patchespkginfo -l (package name)pkginfo -l (package name)Requirements
Component(s) of CFSVERSION STRINGTIME STAMPREQUIRED patch(es) before upgrade
VRTScavf1.1,REV=BUILD62001-04-09N/A
VRTSvxfs3.4,REV=GA032000-11-21N/A
VRTSglm3.4,REV=GA022000-11-20N/A
VRTScfsdc3.4,REV=GA032000-11-21N/A
VRTSvcs1.3.02000092714N/A
VRTSllt1.3.009/27/00-15:42:40N/A
VRTSgab1.3.02000092714N/A
VRTSperl1.3.0m2714N/A
VRTSvcsdc1.3.02000.10.27-13.18.29N/A
VRTScscm1.3.0 (JDK1.1.8/Swing1.1.1)2000092714N/A
VRTSlic1.0,REV=GA022000-11-20N/A
VRTSvmdev3.1.1,REV=01.30.2001.15.0830-January-2001N/A
VRTSvmman3.1.1,REV=01.30.2001.22.2030-January-2001N/A
VRTSvmsa3.1.1,REV=02.10.2001.07.42February 10, 2001N/A
VRTSvxvm3.1.1,REV=01.30.2001.22.2130-January-2001N/A
VRTSvmdoc3.1.1,REV=02.12.2001.18.2330-January-2001N/A
patch 110435-023.4,REV=PATCH01_BUILD72001_05_02110383-01, 108528-02, 108901-03
patch 110436-013.4,REV=PATCH01_BUILD62001_04_06110435-01
patch 110444-011.3.02000092714N/A
patch 110447-011.3.009/27/00-15:42:40N/A
patch 110707-011.3.02000092714N/A
patch 111118-023.1.1,REV=01.30.2001.22.2130-January-2001109529-04
patch 111122-013.1.1,REV=02.10.2001.07.42February 10, 2001N/A




Legacy ID



246583


Article URL http://www.symantec.com/docs/TECH19610


Terms of use for this information are found in Legal Notices