HP Serviceguard Version A.11.20 Release Notes, February 2014

• If you are upgrading both the Quorum Server and Serviceguard, upgrade the Quorum Server
before you upgrade Serviceguard.
CAUTION: If you are using an alternate Quorum Server subnet (page 31), and you are not
already running Quorum Server version A.04.00, you must upgrade to version A.04.00
before you proceed; see “Quorum Server Upgrade Required if You Are Using an Alternate
Address” (page 9).
• If you are upgrading from a release earlier than A.11.16, see “Access changes as of A.11.16”
(page 34).
• For information about supported Serviceguard versions, see the support matrix at http://
www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard.
CAUTION: Make sure that no package is in maintenance mode when you upgrade Serviceguard;
see “Maintaining a Package: Maintenance Mode” in chapter 7 of Managing Serviceguard for
more information about maintenance mode.
Upgrade Using DRD
DRD stands for Dynamic Root Disk. Using a Dynamic Root Disk on HP-UX 11i v3 allows you to
perform the update on a clone of the root disk, then halt the node and reboot it from the updated
clone root disk.
You can obtain the latest version of the DRD software free from http://www.hp.com/go/drd.
IMPORTANT: Use the clone disk only on the system on which it was created. Serviceguard does
not support booting from a clone disk made on another system (sometimes referred to as DRD
re-hosting).
Rolling Upgrade Using DRD
A rolling upgrade using DRD is like a rolling upgrade, but is even less disruptive because each
node is down for a shorter time. It is also very safe; if something goes wrong you can roll back to
the original (pre-upgrade) state by rebooting from the original disk.
This method is the least disruptive, but you need to make sure your cluster is eligible; see
“Requirements for Rolling Upgrade to A.11.20” (page 46) and “Restrictions for DRD Upgrades”
(page 45).
If, after reading and understanding the restrictions, you decide to perform a rolling upgrade using
DRD, follow the instructions under “Performing a Rolling Upgrade Using DRD” in Appendix D of
the latest edition of Managing Serviceguard, which you can find at the address given under
“Documents for This Version” (page 34).
Non-Rolling Upgrade Using DRD
In a non-rolling upgrade with DRD, you clone each node's root disk and apply the upgrade to the
clone, then halt the cluster and reboot each node from its updated clone root disk.
This method involves much less cluster down time than a conventional non-rolling upgrade, and is
particularly safe because the nodes can be quickly rolled back to their original (pre-upgrade) root
disks. But you must make sure your cluster is eligible; see “Restrictions for DRD Upgrades” (page 45).
If, after reading and understanding the restrictions, you decide to perform a non-rolling upgrade
using DRD, follow the instructions under “Performing a Non-Rolling Upgrade Using DRD” in
Appendix D of the latest edition of Managing Serviceguard, which you can find at the address
given under “Documents for This Version” (page 34).
44 Serviceguard Version A.11.20 Release Notes