 |
» |
|
|
 |
The clu_upgrade command, described in clu_upgrade(8), controls the overall flow of a rolling upgrade and ensures that the stages are run in order. During the install stage, you run one or more of installupdate, dupatch, or nhd_install to load and install software. These commands are rolling upgrade aware; they are modified to understand which actions they are allowed to take during the install and roll stages of a rolling upgrade. When you start a rolling upgrade, the cluster is running the software from the previous release. For the first part of any rolling upgrade, you are running the clu_upgrade command that is already installed on the cluster. If a new version is installed during the rolling upgrade, there may be minor differences in the on-screen display and behavior between the two versions of the command. The following two tables show at which stages during a rolling upgrade new versions of upgrade commands, if shipped with the kits being installed, become available during a rolling upgrade:[2] Table 4-4 Stages and clu_upgrade Versions When Performing a Rolling Upgrade from Version 5.1A Stage | Version 5.1A | Next Release[1] | Comments |
---|
Preparation | X | | The currently installed (old) version of clu_upgrade is always run in this stage. | Setup | X | | The currently installed (old) version of clu_upgrade is always run in this stage. If performing an update installation, the new version of the clu_upgrade is extracted from the TruCluster software kit and installed at /usr/sbin/clu_upgrade, replacing the old version. Because this replacement is done before tagged files are created, all members will use the new clu_upgrade throughout the remainder of the rolling upgrade. | Preinstall | | X | If the rolling upgrade includes an update installation, all members use the new version of clu_upgrade installed during the setup stage. (Otherwise, members continue to run the current version of clu_upgrade.) | Install | | X | If the rolling upgrade includes an update installation, all members use the version of clu_upgrade installed during the setup stage. During the update installation, a new version of installupdate replaces the old one. A patch kit always installs the latest version of dupatch. If performing a patch, and if the patch kit includes a new version of clu_upgrade, the new version is installed and will be used by all cluster members starting with the postinstall stage. | Postinstall | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Roll | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Switch | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Clean | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. |
Table 4-5 Stages and clu_upgrade Versions When Performing a Rolling Upgrade from Version 5.1B Stage | Version 5.1B | Next Release[1] | Comments |
---|
Preparation | X | | The currently installed (old) version of clu_upgrade is always run in this stage. | Setup | X | | The currently installed (old) version of clu_upgrade is always run in this stage. If performing an update installation, the new version of the clu_upgrade is extracted from the TruCluster software kit and installed at /usr/sbin/clu_upgrade, replacing the old version. Because this replacement is done before tagged files are created, all members will use the new clu_upgrade throughout the remainder of the rolling upgrade. | Preinstall | | X | If the rolling upgrade includes an update installation, all members use the new version of clu_upgrade installed during the setup stage. (Otherwise, members continue to run the current version of clu_upgrade.) | Install | | X | If the rolling upgrade includes an update installation, all members use the version of clu_upgrade installed during the setup stage. During the update installation, a new version of installupdate replaces the old one. A patch kit always installs the latest version of dupatch. If performing a patch, and if the patch kit includes a new version of clu_upgrade, the new version is installed and will be used by all cluster members starting with the postinstall stage. | Postinstall | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Roll | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Switch | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. | Clean | | X | If a new version of clu_upgrade was installed in either the setup stage or the install stage, all members use the new version. |
|