When you run installvcs
on cluster systems that currently runs VCS 4.1 MP2, the program guides you through an upgrade procedure. The example upgrade demonstrates how to upgrade VCS 4.1 to VCS 5.0 on nodes north and south using installvcs program.
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
CampusCluster
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
main.cf
to a location on the cluster node.
main.cf
located under /etc/VRTSvcs/conf/config
.
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.
Start the installvcs program to automatically upgrade the cluster nodes.
cluster_server
directory and start the installvcs program:
ClusterService
group, if it is defined):
VCS configuration files exist on this system with the following information: No checks have been made to ensure the validity of the configuration.
Do you want to upgrade to version 5.0 on these systems using the
current configuration? [y,n,q,?] (y) y
The installer program verifies that you systems meet the requirements for upgrading.
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......Linux 2.6.5-7.244-smp
Checking VCS installation on north.................... 4.1.10.00
Checking VCS installation on south.................... 4.1.10.00
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
The installer program is ready to remove the RPMs from VCS version 4.1 and install the 5.0 RPMs on each node after verifying the requirements.
To remove VCS RPMs from previous versions and add 5.0 RPMs
Additional RPMs are typically installed to simplify future upgrades.1) Required Veritas Cluster Server RPMs - 397 MB required
Enter
at the prompt.
installvcs will upgrade or install the following VCS RPMs:
VRTSperl Veritas Perl 5.8.8 Redistribution
VRTSicsco Symantec Infrastructure Core Services Common
VRTSpbx Symantec Private Branch Exchange
VRTSsmf Symantec Service Management Framework
VRTSatClient Symantec Product Authentication Service Client
VRTSatServer Symantec Product Authentication Service
VRTSspt Veritas Software Support Tools
SYMClma Symantec License Inventory Agent
VRTSllt Veritas Low Latency Transport
VRTSgab Veritas Group Membership and Atomic Broadcast
VRTSvcs Veritas Cluster Server
VRTSvcsmg Veritas Cluster Server Message Catalogs
VRTSacclib Veritas ACC Library
VRTSvcsag Veritas Cluster Server Bundled Agents
VRTSvcsdr Veritas Cluster Server Disk Reservation Modules and
VRTSvcsmn Veritas Cluster Server Man Pages
VRTSvcsdc Veritas Cluster Server Documentation
VRTSjre Veritas Java Runtime Environment Redistribution
VRTSjre15 Veritas Java Runtime Environment Redistribution
VRTScscw Veritas Cluster Server Configuration Wizards
VRTScscm Veritas Cluster Server Cluster Manager
VRTScssim Veritas Cluster Server Simulator
VRTSweb Veritas Java Web Server
VRTScutil Veritas Cluster Utilities
VRTScmcs Veritas Cluster Management Console (Single Cluster
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 RPMs
Are you ready to begin the Veritas Cluster Server upgrade at
this time? [y,n,q] (y) y
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
After the installvcs program upgrades the nodes, you can proceed to start VCS using the installvcs program.
Do you want to start Veritas Cluster Server processes now? [y,n,q] (y)
n
and do not start VCS here. Edit the main.cf
file to:
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.
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.
n
and do not start VCS here.
Open the main.cf
file and ensure that absolute path names are specified for the Apache resource attributes. Then attempt to start VCS.
y
to start VCS.
Unfreezing NFSGroup....................................... Done
Unfreezing myshare........................................ Done
Unfreezing testgrp........................................ Done
Onlining ClusterService Group on north.................... Done
After starting the cluster server processes, the upgrade is complete.
/opt/VRTS/install/logs/installvcs-
unique string
/
directory.