Using MySQL Toolkit in a HP Serviceguard Cluster Revision README: B.06.00

having the instance to migrate to standby node. The following
procedure should be followed during maintenance:
Note: The example assumes that the package name is mysql_1,
package directory is /etc/cmcluster/pkg/MySQL1 and the
MySQL DATADIR is configured as /MySQL_1/mysql
- Disable the failover of the package through cmmodpkg command.
$ cmmodpkg -d mysql_1
- Pause the monitor script
Create an empty file /etc/cmcluster/pkg/MySQL1/mysql.debug
as shown below:
$ touch /etc/cmcluster/pkg/MySQL1/mysql.debug
Toolkit monitor script which continuously monitors MySQL process,
would now stop monitoring this daemon process. A message
"MySQL toolkit pausing monitoring and entering maintenance mode"
appears in the Serviceguard Package Control script log.
- If required, stop the MySQL database instance as shown below:
$ /etc/cmcluster/pkg/MySQL1/toolkit.sh stop
- Perform maintenance actions (Example: changing the configuration
parameters in the parameter file of the MySQL instance. If this
file is changed, please remember to distribute the new file to all
cluster nodes).
- Start the MySQL database instance again if you stopped it
$ /etc/cmcluster/pkg/MySQL1/toolkit.sh start
- Allow monitoring scripts to continue normally as shown below:
$ rm -f /etc/cmcluster/pkg/MySQL1/mysql.debug
A message "Starting MySQL toolkit monitoring again after
maintenance" appears in the Serviceguard Package Control script
log.
- Enable the package failover
$ cmmodpkg -e mysql_1
Note: If the package fails during maintenance (e.g., the node
crashes), the package will not automatically fail over to an
adoptive node. It is the responsibility of the user to start
the package up on an adoptive node. Please refer to the
manual "Managing Serviceguard" for more details.