HP OpenVMS 8.x manual How a Rolling Upgrade Works, Log in locally to the System account

1.Log in locally to the SYSTEM account.

If you have more than one system disk, make sure that you have performed the preupgrade tasks on each system disk that you are upgrading. Make sure the target system disk is not mounted on any other node in the cluster and remains dismounted during the upgrade. It should be mounted only on the system that is performing the upgrade. (For information about dismounting disks, see Section 5.5.2.3 (page 91).) Then go to Chapter 6 (page 95) and perform an upgrade on each system disk. You do not have to reboot the operating system media for each upgrade. You only need to choose option 1 on the menu for each upgrade.

2.Shut down all systems by entering the following command on each system (satellite nodes first, then the boot nodes):

$ @SYS$SYSTEM:SHUTDOWN

3.When the procedure asks whether an automatic system reboot should be performed, enter N (NO).

4.Choose the CLUSTER_SHUTDOWN option.

5.When the shutdown procedure is finished on all nodes, halt each system by either pressing Ctrl/P or Halt. For more information about halting your Integrity server, see Section A.7.1 (page 184).

6.If you have only one system disk for your cluster, go to Chapter 6 (page 95) to begin the upgrade procedure.

After the upgrade is complete, you are instructed to reboot each computer in the OpenVMS Cluster environment before beginning other postupgrade procedures.

5.5.2Rolling Upgrade

This section describes the following:

•How a rolling upgrade works

•Notes and restrictions

•Preparing your system for a rolling upgrade

5.5.2.1How a Rolling Upgrade Works

A rolling upgrade allows you to have a mixed-version cluster. During a rolling upgrade, you keep some of the computers in the cluster running and available while you upgrade others (you must have more than one system disk). You upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster.

5.5.2.2Notes and Restrictions

The following restrictions apply to rolling upgrades. For additional compatibility issues and restrictions information, 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.

•The system being upgraded does not attempt to access any disk that is being accessed by one or more of the remaining OpenVMS Cluster systems.

•The remaining OpenVMS Cluster systems do not attempt to access the target disk of the system being upgraded.

If the target disk being upgraded is locally attached to the system performing the upgrade, then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system booted from the operating system media does not MSCP serve local disks.) HP recommends that, whenever possible, you perform the upgrade on a local disk or that you perform a concurrent upgrade.

During the upgrade, be sure that the target disk you select, as well as any disk you access from the DCL menu option, is either a local disk or one that is not being accessed by any of

90 Preparing to Upgrade in an OpenVMS Cluster Environment