Updating the Cluster Software

Before upgrading Red Hat Cluster Manager, be sure to install all of the required software, as described in the Section called Kernel Requirements in Chapter 2. The cluster software can be updated while preserving the existing cluster database. Updating the cluster software on a system can take from 10 to 20 minutes.

To update the cluster software while minimizing service downtime, follow these steps:

1. On a cluster system in need of an update, run the cluadmin utility and back up the current cluster database. This will preserve the existing cluster configuration database. For example, at the cluadmin> prompt, perform the following command:

   cluster backup

2. Stop the cluster software on the first cluster system to be updated by invoking the cluster stop command located in the System V init directory. For example:

   /sbin/service cluster stop

3. Install the latest cluster software on the first cluster system to be updated by invoking. However, when prompted by the cluconfig utility whether to use the existing cluster database, specify yes.

4. Stop the cluster software on the second cluster system to be update by invoking the cluster stop command located in the System V init directory. At this point, no services are available.

5. Run cluconfig on the first updated cluster system. When prompted whether to use the existing cluster database, specify yes. The cluster configuration prompts will be displayed with default parameters set to those of the current configuration. If no changes are necessary, just press [Enter] to accept the existing value[s].

6. Start the cluster software on the first updated cluster system by invoking the cluster start command located in the System V init directory. At this point, services may become available. For example:

   /sbin/service cluster restart

7. Install the latest cluster software on the second cluster system to be updated by invoking the following command:

   rpm --upgrade clumanager-x.rpm

   Replace x with the version of Red Hat Cluster Manager currently available.

8. On the second updated cluster system,run the /sbin/cluconfig --init=raw_file command, where raw_file specifies the primary quorum partition. The script will use the information specified for the first cluster system as the default. For example:

   cluconfig --init=/dev/raw/raw1

9. Start the cluster software on the second cluster system by invoking the cluster start command located in the System V init directory. For example:

   /sbin/service cluster start