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

Note:
These sections only describe the stages. Use the procedure in “Rolling Upgrade Procedure” to
perform a rolling upgrade.
• Preparation stage (“Preparation Stage”)
• Setup stage (“Setup Stage”)
• Preinstall stage (“Preinstall Stage”)
• Install stage (“Install Stage”)
• Postinstall stage (“Postinstall Stage”)
• Roll stage (“Roll Stage”)
• Switch stage (“Switch Stage”)
• Clean stage (“Clean Stage”)
Preparation Stage
Run LevelWhere RunCommand
multi-user modeany member
clu_upgrade -v check setup
lead_memberid
During the preparation stage, you back up all important cluster data and verify that the cluster
is ready for a roll. Before beginning a rolling upgrade, do the following:
1. Choose one member of the cluster as the first member to roll. This member, known as the
lead member, must have direct access to the root (/), /usr, /var, and, if used, i18n file
systems.
Make sure that the lead member can run any critical applications. You can test these
applications after you update this member during the install stage, but before you roll any
other members. If a problem occurs, you can try to resolve it on this member before you
continue. If you cannot resolve a problem, you can undo the rolling upgrade and return the
cluster to its pre-roll state. (“Undoing a Stage” describes how to undo rolling upgrade stages.)
2. Back up the clusterwide root (/), /usr, and /var file systems, including all member-specific
files in these file systems. If the cluster has a separate i18n file system, back up that file
system. In addition, back up any other file systems that contain critical user or application
data.
Note:
If you perform an incremental or full backup of the cluster during a rolling upgrade, make
sure to perform the backup on a member that is not running on tagged files. If you back up
from a member that is using tagged files, you will only back up the contents of the .Old..
files. Because the lead member never uses tagged files, you can back up the cluster from the
lead member (or any other member that has rolled) during a rolling upgrade.
Most sites have automated backup procedures. If you know that an automatic backup will
take place while the cluster is in the middle of a rolling upgrade, make sure that backups
are done on the lead member or on a member that has rolled.
3. If you plan to run the installupdate command in the install stage, remove any blocking
layered products listed in Table 4-6 “Blocking Layered Products” that are installed on the
cluster.
62 Patching a Cluster