Document revision date: 19 July 1999 | |
Previous | Contents | Index |
This chapter describes how to upgrade a VAXcluster environment. Refer
to OpenVMS Cluster Systems for more detailed information on VAXcluster
environments.
6.1 Mixed-Version Support
If your cluster environment has both VAX and Alpha systems, also refer to Migrating an Environment from OpenVMS VAX to OpenVMS Alpha.
OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 provide two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems. These two support types are warranted and migration.
Warranted support means that Compaq has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations.
Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Compaq has qualified the versions for use together in configurations that are migrating in phases to a newer version of OpenVMS VAX or to OpenVMS Alpha. Problem reports submitted against these configurations will be answered by Compaq. However, in exceptional cases Compaq may request that you move to a warranted configuration as part of answering the problem.
Migration support will help you move to warranted OpenVMS Cluster version mixes with minimal impact on your cluster environment. Table 6-1 shows the level of support provided for all possible version pairings.
V6.2 | V7.1 | V7.2 | |
---|---|---|---|
V6.2 | WARRANTED | Migration | Migration |
V7.1 | Migration | WARRANTED | Migration |
V7.2 | Migration | Migration | WARRANTED |
Compaq does not support the use of Version 7.2 with Version 6.1 (or earlier versions) in an OpenVMS Cluster environment. In many cases, mixing Version 7.2 with versions prior to Version 6.2 will successfully operate, but Compaq cannot commit to resolving problems experienced with such configurations. |
There are two types of cluster upgrades: concurrent
and rolling. 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 suits your configuration.
6.2.1 Concurrent Upgrades
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 VAX computer. If all systems in the VAXcluster environment are booted from one system disk, you must perform a concurrent upgrade.
For OpenVMS VAX Version 7.2 concurrent upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.1.10 for more information.) |
To perform a concurrent upgrade, go to Section 6.3.
6.2.2 Rolling Upgrades
During a rolling upgrade, you can keep some of the VAX computers in the cluster running while you upgrade others (you must have more than one system disk). The cluster runs temporarily with different versions of the operating system.
For OpenVMS VAX Version 7.2 rolling upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.1.10 for more information.) |
To perform a rolling upgrade, go to Section 6.4.
6.3 Concurrent Upgrade
This section describes the following:
During a concurrent upgrade, you must shut down the entire cluster and
upgrade each system disk and reboot each VAX computer in the cluster.
When the cluster reboots, each VAX computer will be running the
upgraded version of the OpenVMS VAX operating system.
6.3.2 Preparing for a Concurrent Upgrade
To prepare for a concurrent upgrade, use the following procedure:
$ @SYS$SYSTEM:SHUTDOWN |
You cannot use the system disk that you usually use as the quorum disk to hold the save sets from the distribution kit. |
SYSBOOT> USE CURRENT SYSBOOT> SET VOTES 1 SYSBOOT> SET EXPECTED_VOTES 1 SYSBOOT> CONTINUE |
This section describes the following:
During a rolling upgrade, you upgrade each system disk individually,
allowing old and new versions of the operating system to run together
in the same cluster, creating a mixed-version cluster. Because rolling
upgrades allow mixed-version clusters, the systems
that you are not upgrading remain available.
6.4.2 Notes and Restrictions
The following restrictions apply to rolling upgrades:
To prepare for a rolling upgrade, follow these steps:
$ @SYS$SYSTEM:SHUTDOWN.COM |
$ SET CLUSTER/EXPECTED_VOTES |
$ [Ctrl/P] >>> H >>> D/I 14 C >>> C IPC> Q IPC> [Ctrl/Z] |
The upgrade procedure requires exclusive access to the drive that holds the distribution media. Do not mount the distribution media on other nodes. |
* Are the other system disks running OpenVMS V6.2 or higher? |
If you need to add a new CPU supported by OpenVMS VAX Version 7.2 to an existing Version 6.2 VAXcluster, Compaq supports two options, listed in the following preferred order:
This chapter explains the procedure for upgrading a single OpenVMS VAX system disk, including:
You must complete each phase of the upgrade procedure. On most VAX computers, the upgrade procedure continues automatically from phase to phase. Read the screen displays carefully and, if you need to reboot your VAX computer manually, refer to the upgrade and installation supplement for your VAX computer and Appendix C of this manual.
The time required to complete an upgrade varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs.
Before you begin the upgrade procedure, read the overview of the
upgrade procedure described in Chapter 1 and complete the
preupgrade tasks described in Chapter 5. If you are upgrading a
VAXcluster, you must also read Chapter 6.
7.1 Preparing to Boot from [SYSF]
During the upgrade procedure, you are asked to boot the system from the [SYSF] directory on the system disk. The [SYSF] directory is a root directory created on the system disk by the upgrade procedure. It temporarily holds the system files used in the upgrade until the procedure moves the files to their permanent location. The upgrade procedure then removes the [SYSF] directory from the system disk.
If you do not know how to boot from [SYSF], read the upgrade and installation supplement for your VAX computer and Appendix C of this manual.
Ignore any error messages after the first reboot that indicate an
invalid dump header version. These messages are normal and are to be
expected.
7.1.1 Modifying Boot Command Procedures
Some VAX computers require a special command procedure to boot from [SYSF]. If you are performing an upgrade on one of the following VAX computers, you must modify the boot command procedures, DEFBOO and dddGEN before beginning the upgrade procedure:
To modify the boot command procedures, exit from the OpenVMS VAX operating system (but do not shut it down) and enter the appropriate console mode. Make copies of DEFBOO and dddGEN before you modify them. Name the copies DEFBOO.SAV and dddGEN.SAV.
The upgrade and installation supplement for your VAX computer describes the procedures for copying and modifying DEFBOO and dddGEN. Use these procedures to modify DEFBOO and dddGEN so that they specify [SYSF] as the directory from which to boot.
In DEFBOO, change the DEPOSIT command that sets boot flags in register 5 (R5) as follows:
DEPOSIT R5=F0000000 |
In dddGEN, change the DEPOSIT command as follows:
DEPOSIT R5 F0000001 |
If you are upgrading a VAX 8200, 8250, 8300, or 8350 computer, you must
create a boot command procedure that allows you to boot from the [SYSF]
directory before beginning the upgrade. The upgrade and installation
supplement for your VAX computer describes how to create this boot
command procedure.
7.1.3 Configuring Devices
Because you rebooted your system with minimum startup, the system did not automatically configure all devices. However, you might need access to some of the devices to perform the upgrade.
To make sure you can access the devices that might be needed for the upgrade, run SYSGEN to reconfigure the devices on the system and run STARTUP CONFIGURE by entering the following commands:
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> AUTOCONFIGURE ALL SYSGEN> EXIT $ @SYS$SYSTEM:STARTUP CONFIGURE |
This section describes how to start the upgrade procedure using VMSINSTAL. You can type a question mark (?) for help at any time while running VMSINSTAL.
The instructions refer to the source drive and the target drive, where:
Place the distribution compact disc or tape in the source drive. If your OpenVMS VAX distribution kit contains several tapes, put the first one in the drive. The paper labels on the tapes indicate the order in which you use them.
If you are not using an InfoServer device, go to Section 7.2.3.
If you are using an InfoServer device, proceed to the next section.
7.2.2 Upgrading from the InfoServer
If upgrading from an InfoServer device, perform the following steps:
$ @SYS$STARTUP:ESS$STARTUP CLIENT |
%LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy |
$ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND/CONNECT/SYSTEM VAXVMS072 %LADCP-I-BIND, service bound to logical unit DAD$VMS072 (_DADn:) LADCP> EXIT |
To start VMSINSTAL, use the following procedure:
VMSINSTAL displays a message similar to the following, depending on which version of the operating system is currently running on your system:
OpenVMS VAX Software Product Installation Procedure V7.2 It is 13-NOV-1998 at 10:08. Enter a question mark (?) at any time for help. |
VMSINSTAL checks your system's account quotas. If it finds account quotas that are less than it expects, VMSINSTAL displays a message similar to the following:
%VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low. -VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO to -VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log out -VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure. BYTLM: currently 32512; minimum expected 32768 * Do you want to continue anyway [NO]? |
You should have verified that your SYSTEM account quotas were sufficient before beginning the upgrade. (See Section 5.5.8 for the minimum required values and for instructions for modifying quotas and limits.)
To modify the account quotas now, do the following:
To continue the upgrade without modifying the account quotas, type Yes
and press Return.
7.2.4 Backing Up the System Disk
The procedure displays the following message:
* Are you satisfied with the backup of your system disk [YES]? |
If you have made a standalone BACKUP of the system disk, press Return and go to Section 7.2.5.
If you have not made a standalone image backup of the system disk, do the following:
If the upgrade procedure fails and you do not have a current backup of the system disk that you are upgrading, you may not be able to recover to the previous version of the operating system. |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6521PRO_008.HTML |