HP OpenVMS 8.x Adding a New System to an OpenVMS Cluster, Types of Upgrades, Concurrent Upgrade

Before introducing an OpenVMS Version 8.3-1H1 system into an existing OpenVMS Cluster, you might need to install certain patch kits (also known as remedial kits) on cluster members running earlier versions of OpenVMS. In a mixed-architecture cluster, you need to install an LMF patch on any OpenVMS Version 7.3-2 Alpha members. For a complete list of required patch kits, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS Version 8.3 Release Notes.

For information about supporting the Performance Data Collector base software (TDC_RT) in OpenVMS Clusters, see Section 7.8.10.5 (page 135).

5.4 Adding a New System to an OpenVMS Cluster

To add a new OpenVMS Version 8.3-1H1 I64 system to an existing OpenVMS Cluster configuration, all existing Alpha nodes in the cluster must be running OpenVMS Alpha Version 8.3, and all existing OpenVMS I64 nodes must be running OpenVMS I64 Version 8.3 or later. Any node in the cluster that is running an older version of OpenVMS must be upgraded appropriately before you can add a Version 8.3-1H1 node.

Alternatively, any I64 node that needs to be upgraded can be removed temporarily from the cluster and added back after it has been upgraded. This allows you to form a supported cluster immediately, adding nodes back into the cluster as they are upgraded. Note that, depending on the number of nodes being added, you might need to adjust the EXPECTED_VOTES system parameter to reflect the number of voting nodes and any quorum disk votes (if a quorum disk is being used). In addition, for any node being removed from the cluster, you should specify the REMOVE_NODE option during system shutdown so that the quorum for the remaining nodes is correctly adjusted.

5.5 Types of Upgrades

Two types of cluster upgrades are available: a concurrent upgrade and a rolling upgrade. The type of upgrade you use depends on whether you want to maintain the availability of the cluster during the upgrade and whether you have more than one system disk. Review this chapter and then perform the preliminary tasks for the upgrade procedure (concurrent or rolling) that best suit your configuration.

5.5.1 Concurrent Upgrade

This section describes the following:

•How a concurrent upgrade works

•Preparing your system for a concurrent upgrade

5.5.1.1How a Concurrent Upgrade Works

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade each system disk and reboot each computer. When the cluster reboots, each computer will run the upgraded version of the OpenVMS operating system.

If all systems in the OpenVMS Cluster environment are booted from one system disk, you must perform a concurrent upgrade.

5.5.1.2 Preparing Your System for a Concurrent Upgrade

To prepare for a concurrent upgrade, follow these steps:

5.4 Adding a New System to an OpenVMS Cluster 89