 |
» |
|
|
|
This chapter describes which tasks you should
perform prior to beginning an upgrade. Section 4.1 includes a checklist that you can use to
make sure you perform all the tasks described in this chapter. Use the checklist in Table 4-1 to ensure that you perform all necessary tasks
prior to upgrading your system. Table 4-1 Preupgrade Checklist | | Task | Section |
|---|
| Review relevant documentation. | Section 4.2 | | Review notes, cautions,
and restrictions about the following: Upgrade paths to Version 8.3-1H1 Update license requirements Components you choose not to install Upgrade issues after the system disk directory structure
has been changed Licenses and possible reinstallation requirements
for layered products
| Section 4.3 | | Save files that you do not
want deleted by the upgrade procedure. | Section 4.4 | | Prepare the system disk. | Section 4.5 | | Ensure that you have a recent
FEEDBACK.DAT file. | Section 4.6 | | Perform required actions
before upgrading in a volume shadowing environment. | Section 4.7 | | Back up the current system
disk. | Section 4.8 | | Shut down the system. | Section 4.9 |
In addition to reviewing the information in this
chapter, you might need to refer to the following sources of information
as well. OpenVMS Version 8.3-1H1 DocumentsThe Cover
Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers The Software Product Descriptions included with your
distribution kit HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes
OpenVMS Version 8.3 DocumentsInformation in the following documents remains
valid except where superseded by the OpenVMS Version 8.3-1H1 documents
listed previously. The Software Product Descriptions included with your
distribution kit HP OpenVMS Version 8.3 Release Notes HP OpenVMS Version 8.3 New Features and Documentation Overview
Earlier OpenVMS Version Documents
Information in the following documents remains
valid except where superseded by the OpenVMS documents listed previously. HP OpenVMS Cluster Systems Guidelines for OpenVMS Cluster Configurations HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems (specifically, the chapter entitled “Managing System Parameters”),
for information about using AUTOGEN, modifying the system parameters
file (MODPARAMS.DAT), and related operations HP OpenVMS System Management Utilities Reference Manual, for information about using system management utilities such as
SYSMAN and ANALYZE/DISK_STRUCTURE HP OpenVMS Guide to System Security, for information about reestablishing your security environment
after the upgrade
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. 4.3.1 Upgrade Paths | |
You can upgrade directly to OpenVMS
I64 Version 8.3-1H1 from only the following versions of OpenVMS
I64: 4.3.3 Components You Choose Not to Install | |
If you choose not to install optional OpenVMS
networking software (DECnet or TCP/IP) or the DECwindows/Motif GUI
during the upgrade, the upgrade procedure removes these products from
the system disk. Note that TCP/IP Services for OpenVMS is installed
automatically when OpenVMS is installed by HP SIM provisioning. 4.3.4 Licenses and Layered Products | |
The upgrade procedure is designed so that you
do not need 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 OpenVMS license
and layered product licenses intact. You do not need to reinstall
these licenses after you upgrade. By default, the upgrade procedure deletes files
that were archived as filename.type_OLD by OpenVMS
remedial kits. If you do not want these files deleted, you can rename
them before you perform the upgrade. Alternatively, you can have
the upgrade procedure save them by responding to the prompts, as described
in Section 6.4.4. The following sections describe how to prepare
the system disk for the upgrade. Operations include the following: Checking for appropriate
directory structure and preserving your security protections Checking the SYSCOMMON
directories Examining the system disk Checking the size of the
system disk Returning authorization
and AGEN$INCLUDE files to the system disk Verifying system parameters
4.5.1 Checking the Directory Structure and Preserving Your Security
Protections | |
If you changed the directory structure on your
system disk, the upgrade procedure does not work correctly. Restore
your system disk to a standard directory structure before you attempt
an upgrade. The OpenVMS upgrade procedure provides new files
and directories in the directory [VMS$COMMON...]. If you have any
special protections and access control lists (ACLs), you need to reapply
them to reestablish the security environment you currently have.
For more information about creating and maintaining a secure environment,
see the HP OpenVMS Guide to System Security manual. 4.5.2 Checking the SYSCOMMON Directories | |
For the upgrade to be successful, the SYSCOMMON
directories in all system roots must be aliases (or hard links) for
the VMS$COMMON directory. To check whether this is the case, enter
the following commands if you are booted from the system disk that
you are upgrading, and compare the displayed file identifiers to ensure
that they are all the same: $ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR |
If you did not boot from the system disk that
you are upgrading, mount the disk to be upgraded and specify the actual
device name in the command. For example, if the system disk to be
upgraded is mounted on DKA100, you would use commands similar to the
following: $ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[SYS*]SYSCOMMON.DIR |
Output from the first command should list a single
file. Output from the second command should list one file for each
system root on the disk. Check whether the file ID is the same for
all of the listed files and take action as follows: If all the file IDs are
the same, continue with the procedure described in the next section. If all the file IDs are
not the same, this system disk does not have the directory structure
that OpenVMS requires, and the upgrade will not succeed. For assistance
on resolving this, contact your software support representative.
4.5.3 Examining the System Disk | |
Examine and repair (if necessary) the system disk
using the ANALYZE/DISK_STRUCTURE command. (See the HP OpenVMS System Management Utilities Reference Manual: A-L for more information about this command.) Use the following procedure: Analyze
the system disk for inconsistencies and errors in the file structure
by entering the following command: $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE |
Ignore the following message: %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS |
If
you find any other errors on the system disk, repair the errors by
entering the following command: $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE |
Repeat steps 1 and 2 until no errors (other than
the one shown in step 1) are returned.
4.5.4 Checking the Size of the System Disk | |
It is difficult to determine in advance how many
blocks of disk space you 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: The maximum amount of disk space you need is approximately 675,000 blocks, but
your system might use substantially less.
To see how much space you have on the system disk,
enter the following command: $ SHOW DEVICE SYS$SYSDEVICE |
4.5.5 Returning Authorization and AGEN$INCLUDE Files to the System
Disk | |
If you place authorization and AGEN$INCLUDE files
on disks other than the system disk, the upgrade procedure will not
find these files. This is because the other disks are not mounted
during the upgrade. In addition, the logical names you set up to
point to these files are not defined during the upgrade. The following
sections explain how to make these files available to the upgrade
procedure. 4.5.5.1 Authorization FilesOpenVMS allows you to relocate certain system
files (mostly authorization files) off the system disk. You do this
by copying the files to another location and then defining logical
names as documented in the file SYS$MANAGER:SYLOGICALS.TEMPLATE.
The logical names are defined in SYS$STARTUP:SYLOGICALS.COM. When you boot your system from the OpenVMS operating
system media, the logical names pointing to these files are not defined,
and the disks where they are located are not mounted. Because of
this, the upgrade cannot access the relocated files, possibly resulting
in an incorrect or incomplete upgrade. The upgrade might finish without
error, but the files might not be in place as expected. Before upgrading your system, check the definitions
of these logical names on your system. (If a file has not been relocated,
the corresponding logical name might not be defined. This is acceptable.)
If any logical name points to a location or file name other than the
location and file name listed in Table 4-2, return the file to the default location and
file name. To prevent the system from referencing the files located
off the system disk, either delete the associated logical name (using
the DCL command DEASSIGN/SYSTEM/EXEC), or shut down the operating
system and reboot from the operating system media. After the upgrade
and before booting the operating system, you can move these files
back to their original locations off the system disk, using the DCL
option (8) from the OpenVMS operating system menu. | | | |  | NOTE: Some files listed in Table 4-2, such as SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA and SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE,
might not exist on your system, depending on certain configuration
settings. For information about these files, see the HP OpenVMS Guide to System Security manual. | | | | |
Table 4-2 Logical Names for Relocated Authorization Files | Logical Name | Location and File Name |
|---|
| LAN$NODE_DATABASE | SYS$SYSTEM:LAN$NODE_DATABASE.DAT | | LMF$LICENSE | SYS$SYSTEM:LMF$LICENSE.LDB | | NETNODE_REMOTE | SYS$SYSTEM:NETNODE_REMOTE.DAT | | NETNODE_UPDATE | SYS$MANAGER:NETNODE_UPDATE.COM | | NETOBJECT | SYS$SYSTEM:NETOBJECT.DAT | | NETPROXY | SYS$SYSTEM:NETPROXY.DAT | | NET$PROXY | SYS$SYSTEM:NET$PROXY.DAT | | RIGHTSLIST | SYS$SYSTEM:RIGHTSLIST.DAT | | SYSUAF | SYS$SYSTEM:SYSUAF.DAT | | SYSUAFALT | SYS$SYSTEM:SYSUAFALT.DAT | | SYSALF | SYS$SYSTEM:SYSALF.DAT | | VMSMAIL_PROFILE | SYS$SYSTEM:VMSMAIL_PROFILE.DATA | | VMS$AUDIT_SERVER | SYS$MANAGER:VMS$AUDIT_SERVER.DAT | | VMS$OBJECTS | SYS$SYSTEM:VMS$OBJECTS.DAT | | VMS$PASSWORD_DICTIONARY | SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA | | VMS$PASSWORD_HISTORY | SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA | | VMS$PASSWORD_POLICY | SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE |
4.5.5.2 AGEN$INCLUDE FilesIf you use the AGEN$INCLUDE feature in SYS$SYSTEM:MODPARAMS.DAT
to include files containing additional parameter settings, and the
files that are being included are not on the system disk, then do
the following before upgrading: Move the files to the system disk. Update the AGEN$INCLUDE entries to reflect the new
locations of these files. For these entries, do not use logical names
that you defined in SYS$STARTUP:SYLOGICALS.COM or elsewhere for your
normal startup procedure. When you boot the system from the OpenVMS
operating system media for an upgrade, your normal startup procedure
is not run, and so these logical names are not defined for the upgrade.
In addition, when you first boot the upgraded system, a special startup
procedure is used.
After the upgrade is complete, you can move these
included files back to their original locations. If you do so, remember
to re-set the AGEN$INCLUDE entries in SYS$SYSTEM:MODPARAMS.DAT. 4.5.6 Verifying System Parameters | |
Verify (and modify if necessary) system parameters.
(For information about verifying and modifying system parameters,
see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems .) During an upgrade,
AUTOGEN initially generates parameter values based on parameter defaults.
However, during the GETDATA phase, AUTOGEN modifies parameter values
based on entries stored in SYS$SYSTEM:MODPARAMS.DAT. In addition,
AUTOGEN analyzes feedback information stored in the AGEN$FEEDBACK.DAT
file and, if the data is valid, adjusts any related parameter values
accordingly. (AUTOGEN considers data as valid if the system has been
up at least for 24 hours and the feedback is no more than 30 days
old.) To ensure that your feedback data is up to date, follow the
instructions in Section 4.6. | | | |  | IMPORTANT: If you modify system parameters, note the following:In general, you should
allow AUTOGEN to calculate system parameters. You can hardcode values
(such as GBLPAGES=value), but doing so overrides
AUTOGEN and might not allow it to set an optimal value based on observed
usage. Whenever possible, use
MIN_parameter values (such as MIN_GBLPAGES) to
set the minimum value that can be set for a parameter by AUTOGEN.
AUTOGEN increases the value if necessary. It also adjusts related
parameters, unless they are hardcoded, in which case information is
provided in the AGEN$PARAMS.REPORT file. Use MAX_parameter values to set a maximum value when you need to limit a parameter
to a known maximum value. Enter numeric values as
integers, without commas (for example, 10000). Enter alphabetic characters
in lowercase or uppercase. HP recommends that you
include comments in the MODPARAMS.DAT file indicating who changed
the value, when it was done, and why it was done. An exclamation
point serves as a comment starter and can appear anywhere on a line.
The following is an example illustrating the modifications recommended
in the preceding bulleted items: ! the following changes made by K.Newcomb on 9/20/03
!
SWAPFILE=0 ! don’t re-size the SWAPFILE on AUTOGEN runs
MIN_gblsections=750 ! required for DECwindows MOTIF
MIN_NPAGEDYN=2750000 ! set npagedyn to a min of 2.75 million |
For more information about using AUTOGEN as recommended,
see Section 7.22. | | | | |
If your system was upgraded previously, a new
SYS$SYSTEM:MODPARAMS.DAT file was created then. This file has comments
and possibly duplicated entries that were created during that upgrade.
If you upgrade again, SYS$SYSTEM:MODPARAMS.DAT can become unnecessarily
large and potentially confusing. HP recommends that you edit and
reorganize SYS$SYSTEM:MODPARAMS.DAT before you upgrade again. | | | | | NOTE: On a cluster system disk, the MODPARAMS.DAT file
should exist in SYS$SYSROOT:[SYSEXE] for each root. You must edit
MODPARAMS.DAT as necessary for each root. | | | | |
Before upgrading your system, HP recommends that
you have a recent AGEN$FEEDBACK.DAT file. This file is in SYS$SPECIFIC:[SYSEXE]
(that is, in [SYSx.SYSEXE], where x is the root; for example, SYS0 or SYS1). In OpenVMS Cluster systems,
this file should exist in each node’s SYS$SPECIFIC directory.
When the system (or each system in a cluster) is rebooted after the
upgrade, AUTOGEN runs. If a recent AGEN$FEEDBACK.DAT file is available,
it is used. The data in this file helps AUTOGEN set system parameters
for your specific applications and workload. | | | | | NOTE: If you do not have a current AGEN$FEEDBACK.DAT
file, AUTOGEN might calculate system parameters that do not reflect
your system's requirements. In that case, multiple cycles of
running AUTOGEN and rebooting might be necessary before all layered
products can be started. In some cases, successful startup can require
additional entries in MODPARAMS.DAT. This should not be necessary
if a current AGEN$FEEDBACK.DAT file is available. | | | | |
If you do not have the AGEN$FEEDBACK.DAT file
on your system, HP recommends that you create a current AGEN$FEEDBACK.DAT
file during a time when your system is running under a typical workload.
To ensure the greatest data reliability, the system should be running
for more than 24 hours but less than 30 days. Enter the following
command: $ RUN SYS$SYSTEM:AGEN$FEEDBACK.EXE |
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 the SYS$SYSTEM:SHUTDOWN.COM procedure; however,
the data captured might not fully reflect the typical workload on
your system. | | | | | IMPORTANT: If you start AUTOGEN without specifying the execution-mode
parameter (FEEDBACK, NOFEEDBACK, or CHECK_FEEDBACK), AUTOGEN uses
the feedback information in its calculations. However, if the feedback
information reflects system up time of less than 24 hours, or if the
feedback information is more than 30 days old, AUTOGEN includes warnings
in the AGEN$PARAMS.REPORT file to alert you to potential problems
with the feedback data. If you wrongly assume the feedback is valid,
the parameter settings might vary significantly from your expectations. If you specify FEEDBACK (or NOFEEDBACK), AUTOGEN
uses (or does not use) the feedback regardless of the data’s
reliability. AUTOGEN proceeds through the SETPARAMS phase (if you
specified SETPARAMS, SHUTDOWN, or REBOOT as the end phase) and sets
system parameters to the values it computed. If you specify CHECK_FEEDBACK, AUTOGEN checks
the validity of the feedback data. If AUTOGEN determines the feedback
is suspect, then AUTOGEN ignores the feedback when computing parameter
values. It stops at the TESTFILES phase and issues a warning in the
report that parameters have not been changed. You must read the report
and decide whether the calculated values are acceptable. You can
either use them (by running the AUTOGEN SETPARAMS phase) or rerun
AUTOGEN with valid feedback data. | | | | |
Because you cannot upgrade
the operating system on a shadowed system disk (the upgrade will fail),
you need to disable shadowing of the system 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 multiple-member 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 access physically, 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. 4.7.1 Setting the Boot Device | |
Be sure your system is set to boot by default
from the disk you intend to upgrade. For OpenVMS I64 systems, HP recommends using the
OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) to
add shadowed system disks in a multiple-member shadow set to the EFI
boot device list and dump device list. Be sure to add all members
to both lists. For more information about setting boot options and
using this utility, see Section A.5.2. 4.7.2 Creating a Nonshadowed Target Disk | |
Perform the steps described in this section to
change one of your existing shadowed system disks to a nonshadowed
disk. | | | | | IMPORTANT: 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 (interactive) boot (see Section A.6.8) on the system disk
you have chosen for your target disk. For OpenVMS I64 systems, enter the following command
at the EFI Shell prompt, where fsn: is the device
associated with the system disk (such as fs1:): Shell> fsn:\efi\vms\vms_loader.efi -flags 0,1 |
At
the SYSBOOT> prompt, enter the following command to disable volume
shadowing of the system disk: SYSBOOT> SET SHADOW_SYS_DISK 0 |
Enter
the CONTINUE command to resume the boot procedure. For example: After
the boot completes, go to Section 4.9.
You now have a nonshadowed system disk that you
can use for the upgrade. HP strongly recommends that you make a backup
copy of the system disk and, if your configuration allows it, upgrade
the backup copy. Then, if there are problems, you still have a working
system disk. | | | | | NOTE: OpenVMS Engineering has encountered cases where
recovery from a failed upgrade has been difficult, expensive, or impossible
because no backup of the preupgrade system disk was available. Various
hardware or software failures or a power failure can make a partially
upgraded system disk unusable. A backup copy might be the only route
to recovery. The minimal time required to make a backup is a very
wise investment. | | | | |
To back up the system disk, follow these steps: Shut
down the system (see Section A.7.2). Boot
the operating system media, following the instructions in Section A.6. Use
the menu system to enter the DCL environment (option 8). Mount
the system device and the target device on which you will make the
backup copy. (If you are backing up to tape, skip to the next step.)
For example, if your system disk is on DKA0: and the target device
is on DKA100:, you might use the following commands. The /OVERRIDE
qualifier used in this example allows you to mount the system disk
without entering its volume label. The /FOREIGN qualifier is required
for the target disk when you use the BACKUP /IMAGE command. $$$ MOUNT /OVERRIDE=IDENTIFICATION DKA0:
$$$ MOUNT /FOREIGN DKA100: |
To
back up the system disk to a magnetic tape, enter the following commands,
where MTA0: is the magnetic tape drive and label is the volume label. Note that the BACKUP command automatically
mounts the tape and begins the backup to it. $$$ INITIALIZE MTA0: label
$$$ MOUNT /OVERRIDE=IDENTIFICATION DKA0:
$$$ BACKUP /IMAGE /LOG DKA0: MTA0:label.BCK |
To
back up to a device other than a magnetic tape drive, enter the BACKUP
command. For example, if your system disk is on DKA0: and your target
disk is on DKA100:, use the following command (the colons are required): $$$ BACKUP /IMAGE /LOG DKA0: DKA100: |
The /IMAGE qualifier causes the
Backup utility to produce a functionally equivalent copy of the system
disk, which is also bootable. The /LOG qualifier causes the procedure
to display the specification of each save set file being processed.
To compare the backed up files to the source files, use the /VERIFY
qualifier. If any discrepancies are detected, the Backup utility
displays an error message indicating the discrepancies. Log
out from the DCL environment. Shut
down the system by selecting option 9 on the menu.
For more complete information about backup operations,
including a description of an alternative method that does not require
booting from the operating system media, see Appendix E. For more information about the Backup
utility, see the HP OpenVMS System Management Utilities Reference Manual: A-L. 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 | Review the checklist at the beginning of this chapter
to verify that you have performed the necessary tasks. Log in to the SYSTEM account. Enter the following command: When the procedure asks whether an automatic system
reboot should be performed, enter N (NO). Go to Chapter 6 to begin the upgrade procedure.
| You are upgrading an OpenVMS Cluster system | Review the checklist at the beginning of this chapter
to verify that you have performed the necessary tasks. Go to Chapter 5.
|
|
Printable version
