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

The clu_upgrade clean command performs the following tasks:
• Verifies that the switch stage has completed, that all members are running the same versions
of the base operating system and cluster software, and that no members are running on
tagged files.
• Removes all .Old.. files.
• Removes any on-disk backup archives that clu_upgrade created.
• If the directory exists, recursively deletes /var/adm/update/TruClusterKit, /var/
adm/update/OSKit, and /var/adm/update/NHDKit.
• If an update installation was performed, gives you the option of running the Update
Administration Utility (updadmin) to manage the files that were saved during an update
installation.
• Creates an archive directory for this upgrade,
/cluster/admin/clu_upgrade/history/release_version, and moves the
clu_upgrade.log file to the archive directory.
Tagged Files
A rolling upgrade updates the software on one cluster member at a time. To support two versions
of software within the cluster during a roll, clu_upgrade creates a set of tagged files in the
setup stage.
A tagged file is a copy of a current file with .Old.. prepended to the copy filename, and an
AdvFS property (DEC_VERSION_TAG) set on the copy. For example, the tagged file for the vdump
command is named /sbin/.Old..vdump. Because tagged files are created in the same file
system as the original files, you must have adequate free disk space before beginning a rolling
upgrade.
Whether a member is running on tagged files is controlled by that member's sysconfigtab
rolls_ver_lookup variable. The upgrade commands set the value to 1 when a member must
run on tagged files, and to 0 when a member must not run on tagged files.
If a member's sysconfigtab rolls_ver_lookup attribute is set to 1, pathname resolution
includes determining whether a specified filename has a .Old..filename copy and whether
the copy has the DEC_VERSION_TAG property set on it. If both conditions are met, the requested
file operation is transparently diverted to use the .Old..filename version of the file. Therefore,
if the vdump command is issued on a member that has not rolled, the /sbin/.Old..vdump file
is executed; if the command is issued on a member that has rolled, the /sbin/vdump file is
executed. The only member that never runs on tagged files is the lead member (the first member
to roll).
68 Patching a Cluster