< Previous  | TOC | Index | Next  >

Upgrading VCS to 5.0

When you run installvcs on cluster systems that currently runs VCS 3.5 MP2 and 4.0 MP3, the program guides you through an upgrade procedure. The upgrade example demonstrates how to upgrade VCS 4.0 to VCS 5.0 on nodes north and south using installvcs program.

Upgrade tasks include:

• Removing deprecated resource types
• Starting the upgrade
• Checking upgrade requirements
• Removing VCS filesets from previous versions and installing VCS 5.0 filesets
• Starting VCS
• Completing the upgrade
• Updating the configuration file
• Using the halogin command for native OS accounts with VCS

Removing deprecated resource types

With VCS 5.0, certain resource type definitions are no longer used. Before you start the upgrade process, you must remove the resources of the deprecated resource types from your cluster configuration. The list of resource types that are not used in VCS 5.0 are:

• ServiceGroupHB
• ClusterMonitorConfig

  ---

    Note   The ClusterConnectorConfig resource type has replaced the ClusterMonitorConfig resource type.

  ---

If you are using the resource type ServiceGroupHB, Symantec recommends the use of I/O fencing.

Perform the following steps to remove the deprecated resource types.

 To remove the deprecated resource types

1. Save the VCS configuration and stop the VCS engine.

   # haconf -dump -makero

   # hastop -all -force

2. Back up the configuration file, main.cf to a location on the cluster node.
3. Edit the main.cf located under /etc/VRTSvcs/conf/config.
   1. Remove the resource of the deprecated resource types.

      You must modify the resource dependencies to ensure that the configuration works properly.

   2. Save the main.cf.
4. Verify the configuration.

   # cd /etc/VRTSvcs/conf/config

   # hacf -verify config

5. Start VCS on the local node.
6. Start VCS on other nodes.

VCS 5.0 does not support gabdiskhb. So, the installvcs program removes the gabdiskhb entry from the /etc/gabtab file.

  Note   Make sure you start VCS on the local node before starting on the other nodes. This ensures that had reads the configuration from the local node and updates it on the remaining nodes.

Starting the upgrade

Start the installvcs program to automatically upgrade the cluster nodes.

 To start the upgrade

1. Log in as superuser.
2. Mount the software disc.

   See Mounting the product disc

3. Ensure that HAD is running.
4. On the node where the disk was mounted, browse to the cluster_server directory and start the installvcs program:

   # ./installvcs

   See Starting the software installation.

5. After viewing a copyright notice, review the report after the program examines the configuration files and discovers the existing cluster configuration (including the ClusterService group, if it is defined):

VCS configuration files exist on this system with the following 
information:
 
 


 		Cluster Name: vcs_cluster2


 		Cluster ID Number: 7


 		Systems: north south


 		Service Groups: ClusterService XYZ_group


 


No checks have been made to ensure the validity of the 
configuration.
 
 VCS version 4.0.3.0 is installed on this system

6. To upgrade to VCS 5.0, press Enter.

Do you want to upgrade to version 5.0 on these systems using the 
current configuration? [y,n,q,?] (y) y
 

Checking upgrade requirements

The installer program verifies that you systems meet the requirements for upgrading.

 To check upgrade requirements

1. Review the output as the program verifies that the upgrade can proceed on the systems.

   The installvcs program checks the operating system level and system-to-system communication. It also creates logs for the VCS update.

installvcs requires that ssh commands used between systems 
execute without prompting for passwords or confirmations.  If 
installvcs hangs or asks for a login password or hangs, stop 
installvcs and run it again with the ssh configured for 
passwordless logins, or configure rsh and use the -rsh option.
 
 


 Checking ssh communication with north....................AIX 5.3


 Checking VCS installation on north...................... 4.0.3.0


 Checking VCS installation on south...................... 4.0.3.0

2. Review the output as the installer checks the licenses that are currently in place on the cluster nodes. The installer also prompts to add additional license keys:

   Checking system licensing

   Installing licensing filesets

   VCS license registered on north

   Do you want to enter another license key for north? [y,n,q](n) n

   VCS license registered on south

   Do you want to enter another license key for south? [y,n,q](n) n

Removing VCS filesets from previous versions
and installing VCS 5.0 filesets

The installer program is ready to remove the filesets from VCS version 4.1 and install the 5.0 filesets on each node after verifying the requirements.

 To remove VCS filesets from previous versions and add 5.0 filesets

1. Review the output as the installer checks for existing filesets.

   Checking installed filesets on north

   Checking installed filesets on south

2. Specify the filesets to be installed on the cluster systems.

Additional filesets are typically installed to simplify future 
upgrades.
 
 1)  All Veritas Cluster Server filesets - 633 MB required


 2) 		Storage Foundation Enterprise HA filesets - 1114 MB required


 Select the filesets to be installed on all systems? [1-2,q,?] 2

3. The installer lists the filesets that will be installed or upgraded. Press Enter at the prompt.

   installvcs will upgrade or install the following VCS filesets:

   VRTSvlic Veritas Licensing

   VRTSperl.rte Veritas Perl 5.8.6 Redistribution

   VRTSicsco Symantec Common Infrastructure

   VRTSpbx Symantec Private Branch Exchange

   VRTSsmf Symantec Service Management Framework

   VRTSat Symantec Product Authentication Service

   VRTSspt Veritas Software Support Tools

   SYMClma Symantec License Inventory Agent

   VRTSveki Veritas Kernel Interface

   VRTSllt.rte Veritas Low Latency Transport

   VRTSgab.rte Veritas Group Membership and Atomic Broadcast

   VRTSvxfen.rte Veritas I/O Fencing

   VRTSvcs.rte Veritas Cluster Server

   VRTSvcsag.rte Veritas Cluster Server Bundled Agents

   VRTSvcs.msg.en_US Veritas Cluster Server Message Catalogs

   VRTSvcs.man Veritas Cluster Server Man Pages

   VRTSvcs.doc Veritas Cluster Server Documentation

   VRTSjre15.rte Veritas Java Runtime Environment Redistribution

   VRTScutil.rte Veritas Cluster Utilities

   VRTScssim.rte Veritas Cluster Server Simulator

   VRTScscw.rte Veritas Cluster Server Configuration Wizards

   VRTSweb.rte Veritas Java Web Server

   VRTScscm.rte Veritas Cluster Server Cluster Manager

   VRTSacclib.rte Veritas ACC Library

   VRTScmcs.rte Veritas Cluster Management Console (Single

   Cluster Mode)

   VRTScmccc.rte Veritas Cluster Management Console Cluster

   Connector

   Press [Enter] to continue:

4. The installer is now ready to upgrade VCS. Press Enter at the prompt.

   installvcs is now ready to upgrade VCS.

   All VCS processes that are currently running must be stopped.

   Are you sure you want to upgrade VCS? [y,n,q] (y) y

   Updating gabtab on north................................... Done

installvcs must now make configuration updates and stop the 
cluster before upgrading VCS filesets
 
 


Are you ready to begin the Veritas Cluster Server upgrade at 
this time? [y,n,q] (y) y
 

5. View the output as the program backs up the types.cf and main.cf and freezes the service group configured in the cluster.

   Backing up types.cf and main.cf............................ Done

   Freezing group XYZ_group................................... Done

   Updating types.cf file .................................... Done

   Updating gabtab on north................................... Done

   Updating gabtab on south................................... Done

6. The program attempts to stop VCS and uninstall the filesets. Progress indicators show the status of these tasks.
7. The program now attempts to install VCS 5.0 filesets. A progress indicator shows the status of the task.
8. The program starts updating the main.cf configuration file on all nodes in the cluster.

Starting VCS

After the installvcs program upgrades the nodes, you can proceed to start VCS using the installvcs program.

 To start VCS

1. The program prompts you to start VCS.

Do you want to start Veritas Cluster Server processes now? 
[y,n,q] (y)
 
  


 If you have an NFS resource configured in the cluster, enter n and do not start VCS here. Edit the main.cf file to include details about the NFSRestart agent. 


  Refer to the Veritas Cluster Server Bundled Agents Reference Guide for details about editing the main.cf file. After editing this file, attempt to start VCS.


 If you have configured resources for Oracle, Sybase, or DB2 databases, enter n and do not start VCS here.


  Refer to the respective Enterprise agent documentation for upgrade information. After upgrading the agents, attempt to start VCS.


 If you have none of the above resources configured on the node, enter y to start VCS.


  Starting VCS: 0%

  Starting VCS: 100%

  

2. The program attempts to unfreeze the service group and online the ClusterService group.

   Unfreezing NFSGroup....................................... Done

   Unfreezing myshare........................................ Done

   Unfreezing testgrp........................................ Done

   Onlining ClusterService Group on north.................... Done

Completing the upgrade

After starting the cluster server processes, the upgrade is complete.

 To complete upgrade

1. Note the locations of the summary and log files that the program creates.

   Upgrade log files and summary file are saved at:

   /opt/VRTS/install/logs/installvcs-unique string/

2. Other files specific to the installer program are also created in the /opt/VRTS/install/logs/installvcs-unique string/ directory.
3. Verify that the cluster is operating properly after the upgrade.

   See Verifying the VCS installation.