HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

NOTE:
◦ If the package fails during maintenance (for example, 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. For more information, see the latest Managing
Serviceguard manual available at http://www.hp.com/go/hpux-serviceguard-docs —>HP
Serviceguard .
This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set
to "yes" in the MySQL toolkit configuration file.
◦ HP suggests you to have different toolkit directories for each package. If two or more
packages share the same toolkit directory and if one package enters the maintenance
mode, it will affect the other package too.
Guidelines to Start Using MySQL Toolkit
Each toolkit is designed with few assumptions that integrate with the respective application and
with HP Serviceguard. HP recommends you to follow the below mentioned guidelines for setting
up the Package using MySQL Toolkit:
Things you must do
1. Name the package the package configuration file and the package control script in a consistent
and self-explanatory protocol.
For example:
package name mysql1
Package configuration file mysql1.ascii
Package control script mysql1.cntl
2. Place the package configuration file, package control file, and toolkit files in separate
directories for each package.
3. Add <Package directory path> /toolkit.sh start | stop in the customer_defined_run_cmds |
customer_defined_halt_cmds functions respectively for the MySQL toolkit.
4. Ensure that the toolkit.sh, hamysql.sh, hamysql.mon and package control script
have execute permission.
Things you must not do
Do not enable "HA_APP_SERVER" in package control script for each of the MySQL packages.
For example:
#HA_APP_SERVER="pre-IP"
#HA_APP_SERVER="post-IP"
Guidelines to Start Using MySQL Toolkit 97