Managing Serviceguard Sixteenth Edition, March 2009

Performing a Non-Rolling Upgrade
Limitations of Non-Rolling Upgrades
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 407).
The following limitations apply to non-rolling upgrades:
Binary configuration files may be incompatible between releases of Serviceguard.
Do not manually copy configuration files between nodes.
You must halt the entire cluster before performing a non-rolling upgrade.
Steps for Non-Rolling Upgrades
Use the following steps for a non-rolling software upgrade:
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 410) 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 410) for more information.)
4. Restart the cluster:
cmruncl
Guidelines for Migrating a Cluster with Cold Install
There may be circumstances when you prefer to do a cold install of the HP-UX operating
system rather than an upgrade. A cold install erases the existing operating system and
data and then installs the new operating system and software; you must then restore
the data.
CAUTION: The cold install process erases the existing software, operating system,
and data. If you want to retain any existing software, make sure you back up that
software before migrating.
Checklist for Migration
Use the following as a checklist to prepare the migration.
CAUTION: This is a checklist, not a precise set of steps.
1. Back up the data, including databases, user and application data, volume group
configurations, etc.
416 Software Upgrades