HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

Throwing the Version Switch
If a patch applied to the system requires the use of a version switch, you will see a message
similar to the following at the end of the dupatch session:
*********************************************************************
Patch OSFPAT00074200510 has been
identified as needing a version switch. Once the following reboot is
complete, please enter the "/var/adm/patch/noroll/noroll_versw"
command from any cluster member.
*********************************************************************
As indicated by the message, you must enter the /var/adm/patch/noroll/noroll_versw
command from any cluster member. This is a manual operation that you must perform after the
reboot is complete. All cluster members must be up prior to running the noroll_versw
command. If they are not, the noroll_versw command will fail and the version switch will
not take place.
After issuing the noroll_versw command, reboot your system to ensure system integrity.
Removing Patches
You cannot use the no-roll process to remove inclusive patch kits because you must run the
versw_enable_delete script (“Run Mandatory Script Before Removing New Style Patch
Kits”), which requires that you reboot each cluster member to remove the patch kit. Because the
no-roll process automatically reboots the system after deleting the patches, you would not be
able to reboot each member as required.
Using the dupclone Script
You can install Version 5.1B-4 and higher on your cluster using an installation method generically
referred to as cloning that uses a tool named dupclone . The process consists of two primary
steps:
• Creating an exact duplicate of an existing system on an alternate set of disk drives.
• Using dupclone to install the patch kit to the alternate disk set. After completion, the system
can immediately be rebooted using the alternate disks.
NOTE:
The examples in this section assume a two-node cluster that uses one disk drive each for the
cluster-wide root, /usr, and /var file systems; one disk drive for each member boot disk; and
1 drive for the quorum disk.
Benefits and Detriments of Cloning
The benefits of cluster cloning include the following:
• The process can be performed in multi-user mode as a replacement for the no-roll installation
method.
• It does not require the shutdown of any cluster members while the patch kit is being installed
• It provides an easy way to reverse the installation by simply rebooting on the original disk
set.
Reasons why cluster cloning may not be right for your cluster include the following:
• It requires a complete cluster reboot and therefore will not be useful for systems required
to be online 24/7 and rely on the rolling upgrade procedure.
• It requires additional hardware. You must have enough spare disk drives that equals or
exceeds the existing system disk set for the cluster root, /usr, /var, and member boot file
systems. This includes the quorum disk. For example, if you have a three-member cluster
Using the dupclone Script 75