HP OpenVMS Systems Documentation
OpenVMS Alpha Version 7.3
This chapter describes which tasks you should perform prior to beginning an upgrade. Tasks described in this chapter include:
In addition to reviewing the information in this chapter, you might need to refer to the following sources of information as well:
5.1 Notes, Cautions, and Restrictions
This section provides important information that can affect the success
of your upgrade. Review the cautions, restrictions, and notes carefully
before you begin the upgrade.
5.1.1 Spiralog File System Not Supported
The Spiralog file system will not work with Compaq OpenVMS Alpha
Version 7.3. If Spiralog is installed on your system, you
must uninstall it before upgrading to Compaq OpenVMS Alpha Version
5.1.2 Upgrade Paths
To upgrade to Version 7.3 of the Compaq OpenVMS Alpha operating system, you must be running Version 6.2x, 7.0, 7.1x, or 7.2x.
If you are upgrading in a cluster environment, rolling upgrades are
supported from Version 7.1x and 7.2x of the
Compaq OpenVMS Alpha operating system. See Chapter 6 for more information
about upgrading clusters.
5.1.3 Update License
To upgrade to Compaq OpenVMS Alpha Version 7.3, you must have an appropriate license. Compaq's software licenses grant the right to use the current version of a product or any previous version of the product at the time of purchase. If you have an Compaq OpenVMS Alpha license prior to Version 7.3 and are not covered by a Software Product Services agreement, which includes the right to use new versions (RTNV), you must purchase an Update License before upgrading to Compaq OpenVMS Alpha Version 7.3.
If you do not have an Update License, please contact your Compaq
support representative who will assist you in obtaining the correct
Product Authorization Key (PAK) needed to access the OpenVMS operating
5.1.4 Files and Directories
If you choose not to install optional Compaq OpenVMS Alpha software during the upgrade, the upgrade procedure removes existing files for those components from the system disk.
If you have changed directory structure on your system disk, the upgrade procedure will not work correctly. Restore your system disk to a standard directory structure before you attempt an upgrade.
The Compaq OpenVMS Alpha Version 7.3 upgrade procedure provides new
files and directories in the directory [VMS$COMMON...]. If you had any
special protections and access control lists (ACLs) before the upgrade,
you need to reapply them to reestablish the security environment you
had previously set up. For more information about creating and
maintaining a secure environment, see the OpenVMS Guide to System Security.
5.1.5 Licenses and Layered Products
The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures.
The upgrade procedure leaves your Compaq OpenVMS Alpha license and layered
product licenses intact. You do not need to reinstall these licenses
after you upgrade.
5.2 Preparing to Upgrade in a Volume Shadowing Environment
Because you cannot upgrade the operating system on a shadowed system disk (the upgrade will fail), you need to disable shadowing on that disk and perform other operations before you can upgrade the operating system.
There are several methods for creating a nonshadowed target disk. This chapter describes how to change one of your existing shadowed system disks in a multimember shadow set to a nonshadowed disk that you can use as your target disk for the upgrade.
If you have a larger configuration with disks that you can physically
access, you may want to use a copy of the system disk as your
target disk. Volume Shadowing for OpenVMS describes two methods you can use to create
this copy (using volume shadowing commands or BACKUP commands) and how
to disable volume shadowing.
5.2.1 Creating a Nonshadowed Target Disk
Change one of your existing shadowed system disks to a nonshadowed disk as follows:
>>> BOOT -FLAGS 0,1 DKA100
SYSBOOT> SET SHADOW_SYS_DISK 0
After you have created a nonshadowed system disk that you can use for
the upgrade, perform the additional preupgrade procedures described in
the balance of this chapter.
5.2.2 Changing the Label
If you want to change the label on the upgrade disk, use the DCL command SET VOLUME/LABEL=volume-label device-spec[:] to perform this optional task. (The SET VOLUME/LABEL command requires write access [W] to the index file on the volume. If you are not the volume owner, you must have either a system UIC or the SYSPRV privilege.)
For OpenVMS Cluster systems, be sure that the volume label is a unique name across the cluster.
If you change the volume label, you must also register that change in the POLYCENTER Software Installation utility database. To do this, use the following command:
$ PRODUCT REGISTER VOLUME old-volume-label device-name
Note that you must supply the old volume label. The new volume label is found by using the device name.
If you need to change the volume label of a disk that is mounted across the cluster, be sure you change the label on all nodes in the OpenVMS Cluster system. The following example shows how you can use the SYSMAN utility to define the environment as a cluster and propagate the volume label change to all nodes in that cluster:
Be sure your system is set to boot from the upgrade disk by default.
Use the SHOW BOOTDEF_DEV and SET BOOTDEF_DEV console commands to
accomplish this task. (See Appendix A for more information.)
5.3 Backing Up the System Disk
Compaq strongly recommends that you make a backup copy of the system disk and, if your configuration allows it, upgrade the backup copy. (If there are problems, you will still have a working system disk.)
To back up the system disk:
For complete information about backup operations, including a
description of an alternate method that does not require booting from
the operating system CD-ROM, see Appendix B.
5.4 Preparing the System Disk
The following sections describe how to prepare the system disk for the upgrade. The operations include the following:
Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE command. (See the OpenVMS System Management Utilities Reference Manual for more information about this command.) Use the following procedure:
$ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE
%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
$ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE
It is difficult to determine in advance how many blocks of disk space you will need for the upgrade. It depends on how many files you have on the target disk already and on how many components you select during the upgrade procedure. However, the following information will help:
To see how much space you have on the system disk, enter the following command:
$ SHOW DEVICE SYS$SYSDEVICE
Verify (and modify if necessary) system parameters, described as follows. (If necessary, see the OpenVMS System Manager's Manual for more information about modifying system parameters.) Any system parameters that you modified and did not enter in SYS$SYSTEM:MODPARAMS.DAT are lost during the upgrade. To retain these parameters, enter their names in SYS$SYSTEM:MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. (When AUTOGEN runs after the upgrade, it uses the values in SYS$SYSTEM:MODPARAMS.DAT.)
For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT:
Compaq recommends that before upgrading your system you should have a recent SYS$SYSTEM:AGEN$FEEDBACK.DAT. In OpenVMS Cluster systems, there should be a copy of this file on each node. When the system (each system in a cluster) is rebooted after the upgrade, AUTOGEN is run. If a recent AGEN$FEEDBACK.DAT is available, it will be used. The data in this file will help AUTOGEN to set system parameters for your specific applications and workload.
You should create a current AGEN$FEEDBACK.DAT during a time when your system is running under a typical workload. When this condition exists, enter the following command:
$ SYS$UPDATE:AUTOGEN SAVPARAMS
This runs very quickly and should not affect the performance of your system while it executes.
You can also specify the SAVE_FEEDBACK option when you execute
SYS$SYSTEM:SHUTDOWN.COM. However, the data captured my not fully
reflect the typical workload on your system.
5.6 Finish and Shutdown
Continue the preupgrade tasks as follows, depending on whether you are upgrading in a standalone or OpenVMS Cluster environment:
|IF ...||THEN ...|
|you are upgrading a standalone system,||
do the following:
|you are upgrading an OpenVMS Cluster system,||
do the following:
5.7 Preupgrade Checklist
Use the following checklist to make sure you have performed all the
tasks before beginning the upgrade:
This chapter describes how to prepare to upgrade in an OpenVMS Cluster environment, depending on the type of upgrade you perform and whether you need to add any new computers to the cluster.
Be sure you have performed the preupgrade tasks described in Chapter 5 before you upgrade your OpenVMS Cluster system.
When you upgrade the operating system in an OpenVMS Cluster environment, be sure the following information is available to review:
Compaq OpenVMS Alpha Version 7.3 and Compaq OpenVMS VAX Version 7.3 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 a staged fashion to a newer version of Compaq OpenVMS VAX or to Compaq 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.
Compaq supports only two versions of OpenVMS running in a cluster at the same time, regardless of architecture. Migration support helps customers move to warranted OpenVMS Cluster pairs. Table 6-1 shows the level of support provided for all possible version pairings.
|Alpha/VAX V7.3||Alpha V7.2x
|Alpha V7.2 x/VAX V7.2||Migration||WARRANTED||Migration|
|Alpha V7.1-2/VAX V7.1||Migration||Migration||WARRANTED|
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.4 Concurrent Upgrade
This section describes the following:
6.4.1 How 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 Alpha computer. When the cluster
reboots, each Alpha computer will be running the upgraded version of
the Compaq OpenVMS Alpha operating system.
If all Alpha systems in the OpenVMS Cluster environment are booted from
one system disk, you must perform a concurrent upgrade.
6.4.2 Preparing Your System for a Concurrent Upgrade
To prepare for a concurrent upgrade:
1 For more information about halting your Alpha computer, see Appendix A.
This section describes the following: