|
HP OpenVMS Alpha Version 7.3-2 Upgrade and Installation... |
Before Upgrading the OpenVMS Alpha Operating System |
|
|
| |
Notes, Cautions, and Restrictions
Upgrade Paths
The following sections describe the various types of upgrades
to Version 7.3-2.
Direct Upgrade Paths
You can upgrade directly to OpenVMS Alpha
Version 7.3-2 from only the following versions of OpenVMS Alpha:
If you are currently running an OpenVMS Alpha system Version 6.2x through 7.1x inclusive, you must do a two-step upgrade: first to Version 7.2-2 or 7.3, and then to Version 7.3-2.
Cluster 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 and reboot every computer. When you reboot, each
computer will be running the upgraded version of the operating system.
Cluster Rolling Upgrades
During a cluster rolling upgrade,
you upgrade each system disk individually, allowing old and new
versions of the operating system to run together in the same cluster.
There must be more than one system disk. The systems that are not
being upgraded remain available.
Only the following OpenVMS Alpha and OpenVMS VAX versions are supported in mixed-version clusters that include OpenVMS Alpha Version 7.3-2:
If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.2-2, 7.3, and 7.3-1 of the OpenVMS Alpha operating system. If you have other versions in a cluster, you cannot do a rolling upgrade until those versions are upgraded to a supported version. See Preparing to Upgrade in an OpenVMS Cluster Environment for more information about upgrading clusters.
 | To upgrade to OpenVMS Alpha Version 7.3-2, you must have an appropriate license. |
HP 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 OpenVMS Alpha license prior to Version 7.3-2 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 OpenVMS Alpha Version 7.3-2.
 | When you initially purchase the OpenVMS Alpha software and license, HP provides you a Product Authorization Key (PAK) that is required to enable the License Management Facility (LMF) to register the license and to validate and authorize subsequent use of the product. A PAK does not provide license or new version rights. For more information on licensing and the License Management Facility, see the OpenVMS License Management Utility Manual. |
If you are upgrading TCP/IP Services for OpenVMS, DECwindows Motif, DECnet, or any third-party products, you might need update licenses.
Components
You Choose Not to Install
If you choose not to install optional OpenVMS Alpha software
during the upgrade, the upgrade procedure removes existing files
for those components from the system disk.
Files and Directories
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 OpenVMS Alpha Version 7.3-2 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 previously set up. For more information about creating and maintaining a secure environment, see the HP OpenVMS Guide to System Security.
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 OpenVMS Alpha license and layered product licenses intact. You do not need to reinstall these licenses after you upgrade.
|
|
