HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

1. Halt all nodes in the cluster:
cmhaltcl -f
2. If necessary, upgrade all the nodes in the cluster to the new HP-UX release. (See Step 3 under
“Running the Rolling Upgrade” (page 361) for more information.)
3. Upgrade all the nodes in the cluster to the new Serviceguard release. (See Step 3 under
“Running the Rolling Upgrade” (page 361) for more information.)
4. Restart the cluster:
cmruncl
Performing a Non-Rolling Upgrade Using DRD
Limitations of Non-Rolling Upgrades using DRD
CAUTION: Stricter limitations apply to an upgrade to A.11.19; do not proceed with an upgrade
to A.11.19 until you have read and understood the Special Considerations for Upgrade to
Serviceguard A.11.19 (page 357).
IMPORTANT: Not all paths that are supported for upgrade are supported for an upgrade using
DRD, and there are additional requirements and restrictions for paths that are supported.
Do not proceed until you have read the “Announcements”, “Compatibility”, and “Installing
Serviceguard” sections of the latest version of the Serviceguard release notes, made sure your
cluster meets the current requirements, and taken any necessary preparation steps as instructed in
the release notes.
You must also make sure you have read and understood the “Restrictions for DRD Upgrades”
(page 359).
In addition, all the limitations listed under “Limitations of Non-Rolling Upgrades” (page 366) apply
to non-rolling upgrades using DRD. You should also read the “Guidelines for Non-Rolling Upgrade”
(page 366) before you proceed.
Steps for a Non-Rolling Upgrade Using DRD
Use the following steps for a non-rolling software upgrade using DRD:
1. Create a clone root disk for each node.
2. Upgrade each clone disk to the new HP-UX release (if necessary), including Serviceguard
(using drd runcmd update-ux), or upgrade Serviceguard alone (using drd runcmd
swinstall).
3. Halt all nodes in the cluster:
cmhaltcl -f
4. Reboot the nodes from their updated clone root disks.
5. Restart the cluster:
cmruncl
6. Verify that the cluster is healthy, the packages can run, and applications are functioning
properly.
If the cluster is not healthy or the packages and applications are not functioning properly, and you
cannot fix the problems, you can revert to the original (pre-upgrade) cluster by halting the cluster
(cmhaltcl), rebooting each node from its original (pre-upgrade) root disk, and restarting the
cluster (cmruncl).
Performing a Non-Rolling Upgrade Using DRD 367