HP Tru64 UNIX Release Notes for Version 5.1B-5 (AA-RVGEE-TE, March 2009)

After running the baselining process on your existing system, you need to begin the
cloning process from the beginning by reduplicating your system on an alternate set
of disks and rerunning the dupatch cloning process. See the Patch Kit Installation
Instructions for information about performing baselining and about the patch cloning
process.
3.3.4 Migrating a Patched Standalone System to a Cluster
Installing only the base patches on a noncluster system omits various patches (including
some security patches) because of dependencies on TruCluster Server patches. Such
patches are not needed on standalone systems. However, if the standalone system is
then clustered using the clu_create command and you attempt to apply the cluster
patches, many patches fail with errors because some prerequisite patches failed.
These errors do not necessarily indicate that the patch process has failed, but they are
numerous, can be confusing and might obscure genuine errors.
The preferred procedure for adding a standalone system into a cluster is as follows:
1. Reinstall the operating system on the standalone system.
2. Run the clu_create command and bring up the standalone system as a cluster
node.
3. Apply all base and cluster patches.
3.3.5 Disable vfast Utility If Running on Cluster Domains
If the vfast utility is running on the TruCluster domains cluster_root and
cluster_var, deactivate it on the domains before installing or removing this kit. To
deactivate vfast on the two domains, use the following command:
# vfast deactivate cluster_root
# vfast deactivate cluster_var
See the vfast(8) reference page for more information.
3.3.6 Creation of Some MFS File Systems Depends on Version Switch
During the installation of this kit, MFS file systems that are 4 GB and larger (or 2 GB
and larger if a 1024-byte sector size is used) cannot be created until after the version
switch is thrown. See the Patch Kit Installation Instructions for information about the
version switch.
3.3.7 Workaround Saves Files to Enable Patch Kit Removal
If you upgrade the operating system and install a patch kit within the same roll, the
contents of the patch backups are inadvertently removed. The result is that the patches
most recently installed cannot be removed because the backups are missing.
The following procedure saves then restores backups so they are available if you later
decided to remove the patch kit:
32 Release Notes