|
HP OpenVMS Version 8.2 Upgrade and Installation... |
Before Upgrading the OpenVMS Alpha Operating System |
|
|
| |
Notes, Cautions, and Restrictions
Upgrade Paths
The following subsections describe the various types of upgrades
to OpenVMS Alpha Version 8.2.
Upgrades to OpenVMS I64 Version 8.2 are not supported; you must do a new installation to obtain OpenVMS I64 Version 8.2.
Direct Upgrade Paths
You can upgrade directly to OpenVMS Alpha
Version 8.2 from only the following versions of OpenVMS Alpha:
If you are currently running an OpenVMS Alpha system Version
6.2x through 7.3 inclusive, you must first upgrade
to Version 7.3-1 or 7.3-2, and then to Version 8.2. Note that standard
support for OpenVMS Alpha Version 7.3-1 systems ends on March 31,
2005. After that, OpenVMS Alpha V7.3-1 systems will not be under Prior
Version Support (PVS). For more information, refer to the OpenVMS
Technical Software Support Service Web site at ftp://ftp.compaq.com/pub/services/software/ovms.pdf.
Cluster Concurrent
Upgrades
During a concurrent upgrade in an OpenVMS
Cluster, 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 or I64 Version 8.2:
For more information about mixed-version OpenVMS Clusters, see Mixed-Version Support in OpenVMS Cluster Systems. In a mixed-architecture cluster, you need to install an LMF patch on any OpenVMS Version 7.3-2 Alpha members.
If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.3-2 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. For more information about upgrading clusters, see Preparing to Upgrade in an OpenVMS Cluster Environment.
 | To upgrade to OpenVMS Alpha Version 8.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 8.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 8.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 about licensing and the License Management Facility, refer to the HP 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. For more information
about checking for appropriate versions of software on your system
and certain products for which you must manually remove older versions,
see
Check for Appropriate Versions of Software on Your System.
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 8.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, refer to the HP OpenVMS Guide to System Security manual.
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.
|
|
