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 might want to use a copy of the
system disk as your target disk. HP 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.
Creating a Nonshadowed
Target Disk Follow the procedure described in this section to change one
of your existing shadowed system disks to a nonshadowed disk.
If you simply use a MOUNT/OVERRIDE=SHADOW_MEMBERSHIP
command to mount the volume to be upgraded, volume shadowing can
overwrite the newly upgraded disk with information from a prior
volume that has not been upgraded.
Shut down all
systems booted from the shadowed system disk.
Perform a conversational boot (see
Halt, Boot, and Shutdown Procedures, if necessary) on the system
disk you have chosen for your target disk. For example:
>>>BOOT -FLAGS 0,1 DKA100
At the SYSBOOT> prompt,
enter the following command to disable volume shadowing on the disk:
SYSBOOT>SET SHADOW_SYS_DISK 0
Enter the CONTINUE command to resume the boot procedure.
For example:
SYSBOOT>CONTINUE
After the boot completes, log in to the system.
You now have a nonshadowed system disk that you can use for
the upgrade.
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. HP strongly recommends that
a volume label contain only alphanumeric characters and, optionally,
the dollar sign ($), underscore (_), and hyphen (-) characters.
You can include other characters in a volume label, but doing so
on a system disk can cause the upgrade procedure to fail.
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
to use the SYSMAN utility to define the environment as a cluster
and propagate the volume label change to all nodes in that cluster:
SYSMAN> SET ENVIRONMENT/CLUSTERSYSMAN> DO SET VOLUME/LABEL=new-labeldisk-device-name:
Setting the Boot
Device 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. (For more information, see
Halt, Boot, and Shutdown Procedures.)
HP OpenVMS Alpha Version 7.3-2 Upgrade and Installation... 
Before Upgrading the OpenVMS Alpha Operating System
