Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

5. Verify that there are no Site Controller packages running on the node.
# cmviewcl -l package -n `hostname`
6. If SGeRAC is configured, halt the Oracle software (RAC, CRS, Clusterware, and OPS) on the
selected node.
7. Halt the node that is selected for upgrade.
# cmhaltnode -f
Instances of all MNP packages running on this node are halted and the failover packages
move to the adoptive node.
8. Edit the /etc/rc.conf.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 0
9. Upgrade the node to the new HP-UX release, Serviceguard, SGeRAC, or Metrocluster version.
10. Edit the /etc/rc.conf.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 1
11. If the Event Monitoring Service (EMS) is configured, restart it.
a. Kill all EMS monitors.
b. Stop all EMS clients.
c. Kill all registrar processes.
d. Kill the p_client demon.
The p_client process is restarted immediately. The EMS registrar and the monitor
processes are restarted automatically when they are needed.
12. Restart the cluster on the upgraded node.
13. Restart all MNP package instances that were previously running on this node.
14. If SGeRAC is configured, restart the Oracle software (RAC, CRS, Clusterware, OPS) on the
node.
15. Repeat steps 2 through 14 for each node in the site before upgrading nodes in the other site
of the cluster.
In the event of a disaster that results in the cluster failing before the rolling upgrade is complete,
restart the cluster using the cmruncl command from a node which has been upgraded to the
latest version of the software.
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 55