Using Serviceguard Extension for RAC, 10th Edition, April 2013

refer to the Serviceguard Compatibility and Feature Matrix, located at www.hp.com/go/
hpux-serviceguard-docs —> HP Serviceguard Extension for RAC.
6. Recreate any user accounts needed for the cluster applications.
7. Recreate the network and storage configurations (Set up stationary IP addresses and create
LVM volume groups and/or CVM disk groups required for the cluster).
8. Recreate the SGeRAC cluster.
9. Restart the cluster.
10. Reinstall the cluster applications, such as RAC.
11. Restore the data.
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 DRD software free from www.software.hp.com — search for “DynRootDisk”.
For more information, go to HP's Dynamic Root Disk Information Library at www.hp.com/go/drd.
IMPORTANT: Use the clone disk only on the system that 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 “Restrictions
for DRD Upgrades” (page 151).
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, at www.hp.com/go/hpux-serviceguard-docs —> HP
Serviceguard.
Non-Rolling Upgrade Using DRD
In a non-rolling upgrade with DRD, you clone each node's root disk, apply the upgrade to the
clone, halt the cluster, and then 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 151).
Restrictions for DRD Upgrades
• Before you proceed, read the sections Upgrading from an Earlier Serviceguard Release and
Rolling Upgrade in the latest version of the release notes for A.11.20.
• Serviceguard A.11.20 is supported on HP–UX 11i v3 only. For more information, see HP-UX
11i v3 Installation and Update Guide at www.hp.com/go/ hpux-core-docs —> HP-UX 11i
v3.
• You can perform a rolling upgrade from A.11.19 to a later release, or from an earlier release
to A.11.19, but you cannot do a rolling upgrade from a pre-A.11.19 release to a post-A.11.19
release.
This is because A.11.19 is the only version of Serviceguard that will allow both the older
version of the cluster manager and the new version (introduced in A.11.19) to coexist during
a rolling upgrade.
If you are upgrading from a pre-A.11.19 release: Start by reading Upgrading from an Earlier
Serviceguard Release and Rolling Upgrade in the release notes. Then, if you decide to upgrade
Upgrade Using DRD 151