|
HP OpenVMS Version 8.2-1 for Integrity Servers... |
Before Upgrading the OpenVMS Operating System |
|
|
| |
Notes, Cautions, and Restrictions
Upgrade Paths
The following subsections describe the various types of upgrades
to OpenVMS I64 Version 8.2-1.
Direct Upgrade Paths
You can upgrade directly to OpenVMS I64
Version 8.2-1 from only the following versions of OpenVMS I64:
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 run 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.
The following OpenVMS I64 and OpenVMS Alpha versions are supported in mixed-version clusters that include OpenVMS I64 Version 8.2-1 (OpenVMS VAX systems are not supported with OpenVMS I64 systems in the same cluster):
For more information about mixed-version OpenVMS Clusters, refer to 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 8.2 to Version 8.2-1 of the OpenVMS I64 operating system. For more information about upgrading clusters, refer to Preparing to Upgrade in an OpenVMS Cluster Environment.
 | To upgrade to OpenVMS I64 Version 8.2-1, 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.
 | When you initially purchase the OpenVMS software and license, HP provides 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 . |
Components
You Choose Not to Install
If you choose not to install optional OpenVMS 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 for certain
products requiring that you manually remove older versions, refer
to
Check for Appropriate Versions of Software.
Files and Directories
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 Version 8.2-1 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, refer to the HP OpenVMS Guide to System Security manual.
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.
|
|
