Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

1. Identify the sites in the Metrocluster and the associated nodes.
# cmviewcl -l node
Select a site to perform the rolling upgrade.
2. Select a node in a site to perform the rolling upgrade.
# cmviewcl –l node -S <site_name>
3. View all the packages running on the selected node.
# cmviewcl -l package -n `hostname`
Identify the Site Controller packages that are running on the node.
4. Move all Site Controller packages running on the selected node to a different node in the
same site using DETACH halt mode.
For more information on moving the Site Controller package, see “Moving the Site Controller
package to a node at the local site” (page 62).
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, then it must be restarted using the following
steps:
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 to 14 for each node in the site before upgrading nodes in the other site of the
cluster.
If a disaster occurs and results in a in the cluster failure before the rolling upgrade is done, restart
the cluster using the cmruncl command from a node which is upgraded to the latest version of
the software.
In the event of a disaster that results in the cluster failing before the rolling upgrade is done, restart
the cluster using the cmruncl command from a node which is upgraded to the latest version of
the software.
Rolling upgrade 67