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

Note:
A rolling upgrade updates the file systems and disks that the cluster currently uses. The roll
does not update the disk or disks that contain the Tru64 UNIX operating system used to
create the cluster (the operating system on which you ran clu_create). Although you can
boot the original operating system in an emergency when the cluster is down, remember
that the differences between the current cluster and the original operating system increase
with each cluster update.
• Patch the cluster's current versions of the Tru64 UNIX base operating system and TruCluster
software software.
• Install a New Hardware Delivery (NHD) kit (the cluster must be running TruCluster software
Version 5.1A or later).
Rolling in a patch kit or an NHD kit uses the same procedure as rolling in a new release of the
base operating system and cluster software. The difference is which commands you run during
the install stage:
• To upgrade the base operating system and cluster software, run installupdate in the
install stage.
• To roll in a patch kit, run dupatch in the install stage. You can invoke dupatch multiple
times in the install stage to roll in multiple patch kits.
If you want to perform a no-roll patch of the cluster, do not run the clu_upgrade command.
Instead run the dupatch command from a cluster member running in multi-user mode.
No-roll patching applies patches quickly and reduces the number of reboots required. It
patches the cluster in one operation. However, it requires a reboot of the whole cluster to
complete the operation, so the cluster is unavailable for a period.
• To install an NHD kit, run nhd_install in the install stage.
Throughout this chapter, the term rolling upgrade refers to the overall procedure used to roll
one or more software kits into a cluster.
As shown in Figure 4-1 “Rolling Upgrade Flow Chart”, you can perform more than one task
during a rolling upgrade.
If the cluster is running Version 5.1A or Version 5.1B, a rolling upgrade can include the task
combinations listed in Table 4-1 “Rolling Upgrade Tasks Supported by Version 5.1A and Version
5.1B”:
Table 4-1 Rolling Upgrade Tasks Supported by Version 5.1A and Version 5.1B
An update installation from Version 5.1A to Version 5.1B
An update installation from Version 5.1B to the next release
A patch of Version 5.1A
A patch of Version 5.1B
The installation of a New Hardware Delivery (NHD) kit onto a Version 5.1A cluster
The installation of an NHD kit onto a Version 5.1B cluster
An update installation from Version 5.1A to Version 5.1B of the base operating system and cluster software, followed
by a patch of Version 5.1B
An update installation from Version 5.1B to the next release of the base operating system and cluster software
followed by a patch of the next release
1
An NHD installation onto a Version 5.1A cluster followed by a patch of Version 5.1A
An NHD installation onto a Version 5.1B cluster followed by a patch of Version 5.1B
Rolling Upgrade 47