Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy for Linux B.12.00.00

Figure 12 Halt and Advance Halt option
Rolling upgrade
Metrocluster configurations follow the HP Serviceguard rolling upgrade procedure. The HP
Serviceguard documentation includes rolling upgrade procedures to upgrade the Serviceguard
version, the operating environment, and other software. This Serviceguard procedure, along with
recommendations, guidelines, and limitations, is applicable to Metrocluster. For more information
on completing a rolling upgrade of HP Serviceguard, see the latest edition of Managing HP
Serviceguard A.12.00.00 for Linux available at http://www.hp.com/go/linux-serviceguard-docs.
Limitations of the rolling upgrade for Metrocluster
The rolling upgrade for Metrocluster has the following limitations:
• The cluster or package configuration cannot be modified until the rolling upgrade is complete.
If the configuration must be edited, upgrade all nodes to the new release, modify the
configuration file, and then copy it to all nodes in the cluster.
• New features of the latest version of Metrocluster cannot be used until all nodes are upgraded
to the latest version.
• More than two versions of Metrocluster cannot run in the cluster while the rolling upgrade is
in progress.
• The rolling upgrade procedure cannot be used as a means of using multiple versions of
Metrocluster software within the cluster. HP recommends that you immediately upgrade all
cluster nodes to the latest version.
• HP Serviceguard cannot be deleted on any node when the rolling upgrade is in progress in
the cluster.
Rolling upgrade 39