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

ManualsBrandsHP ManualsSoftwareHP Serviceguard Enterprise Cluster Master Toolkit

Using MySQL Toolkit in a HP Serviceguard Cluster

===============================================================

Revision: B.06.00

CONTENTS:

A. MySQL Package Configuration Overview

B. Setting Up the Database Server Application

C. Setting Up MySQL with the Toolkit

C.1 Toolkit Overview

C.2 MySQL Configuration File (my.cnf)

C.3 Toolkit Configuration File (hamysql.conf)

D. Package Configuration File and Control Script

E. Applying the Configuration and Running the Package

F. MySQL Database Server Maintenance

G. Do and Don't with MySQL Toolkit

A. DOs

B. DON'Ts

PREFACE

This README file describes the MySQL Toolkit for use in the

HP Serviceguard environment. The README file is intended for

users who want to configure MySQL Database Server application toolkit

under HP Serviceguard cluster environment using MySQL Toolkit. This

toolkit supports the Enterpise MySQL Database Server Application 5.0.56

and later.

It assumes that readers are already familiar with the HP Serviceguard

cluster configuration as well as MySQL Database server concepts and

their installation and configuration procedures.

NOTE: This toolkit supports:

- HP Serviceguard versions

* A.11.19

* A.11.20

- HP-UX 11i v2 and HP-UX 11i v3

At time of publication, this version supports the above mentioned SG,

application and HPUX versions. More recent versions of these

products may be certified with B.06.00. For the latest information,

see the compatibility matrix located at:

http://docs.hp.com/en/ha.html

NOTE:

This version of the toolkit supports both, legacy and modular style

packages.

NOTE:

This version of the toolkit is not supported with VxVM and CFS.

This toolkit consists of a set of shell scripts used by a Package

Summary of content (14 pages)

PAGE 1
Using MySQL Toolkit in a HP Serviceguard Cluster =============================================================== Revision: B.06.00 CONTENTS: A. MySQL Package Configuration Overview B. Setting Up the Database Server Application C. Setting Up MySQL with the Toolkit C.1 Toolkit Overview C.2 MySQL Configuration File (my.cnf) C.3 Toolkit Configuration File (hamysql.conf) D. Package Configuration File and Control Script E. Applying the Configuration and Running the Package F. MySQL Database Server Maintenance G.
PAGE 2
Control Script to start, stop, and monitor the MySQL Database Server. The toolkit works with the Serviceguard package control script, managed by Serviceguard in case of legacy packages and Serviceguard master control script in case of modular packages. Each MySQL Database server instance is configured in its own Serviceguard package.
PAGE 3
For the alert mail notification feature, an additional parameter called ALERT_MAIL_ID is introduced in the ADF. ALERT_MAIL ID: Sends an email message to the specified email address when packages fail.This email is generated only when packages fail, and not when a package is halted by the operator. To send this email message to multiple recipients, a group email ID must be created and specified for this parameter. When an email ID is not specified for this parameter, the script does not send out this email.
PAGE 4
* (shared config) by filesystem putting the configuration files in a shared * (local config) by putting the configuration files on a single node, then replicating the files to all other nodes in the cluster ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Local Configuration If you opt to store the configuration files on a local disk, the configuration MUST be replicated to local disks on all nodes configured to run the package.
PAGE 5
As a result, all (package) resources are halted. 2. The relocatable IP address is removed from this node. 3. File systems are unmounted and all volume groups assigned to this package are deactivated. Standby Node -----------4. Volume groups are activated and file systems are mounted. 5. The relocatable IP address is moved over to the new node. 6. All resources are started up, and the database is brought up. 7. Clients will (continue to) connect through the same (relocatable) IP address.
PAGE 6
2. Following the instructions in the documentation for MySQL, create the database on the lvol in /MySQL_1. This information may be viewed online at the following link: http://www.mysql.com/documentation/mysql/bychapter/ manual_Tutorial.html#Creating_database 3. Copy the configuration file "/etc/my.cnf" to "/MySQL_1/my.cnf". 4. Modify "/MySQL_1/my.cnf" to configure the DB for your unique environment.
PAGE 7
- Attribute Definition File (mysql) For every parameter in the legacy toolkit user configuration file, there is an attribute in the ADF. It also has an additional attribute TKIT_DIR which is analogous to the package directory in the legacy method of packaging. The ADF is used to generate a package ASCII template file. - Module Script (tkit_module.sh) This script is called by the Master Control Script and acts as an interface between the Master Control Script and the Toolkit interface script (toolkit.sh).
PAGE 8
- Create a soft link named "mysqld_safe" in the MySQL installation directory (typically /usr/bin for RH" to point to "safe_mysqld" CMD> ln -s /usr/bin/mysqld_safe /usr/bin/safe_mysqld - Grant the execute permission to the newly created link. CMD> chmod 755 mysqld_safe ===================================================================== NOTE: The following sections in this document describe the legacy mode of Serviceguard packages.
PAGE 9
not be failed over to the adoptive node. To continue monitoring and turn off maintenance mode, you should remove the "mysql.debug" file. The user should ensure that the MySQL instance is running properly before exiting the maintenance phase, since monitoring of the instance will resume once out of the maintenance phase. 4. RETRY_TIMES=0 This variable is recommended to be set to "0". This will multiply the SERVICE_RESTART of the MySQL package service (monitor).
PAGE 10
SERVICE_NAME : "mysql_monitor" # Service Name [control script parameters] VG : vgMySQL # VG created for this package LV : /dev/vgMySQL/lvol1 # Logical vol created in VT FS : /MySQL_1 # File system for DB FS_TYPE : "ext2" # FS type is "Extended 2" FS_MOUNT_OPT : "-o rw" # mount with read/write options SUBNET : "192.70.183.0" # Package Subnet IP : "192.70.183.171" # Relocatable IP #The service name must be the same as defined in the package #configuration file.
PAGE 11
E. Applying the Configuration and Running the Package Once the database has been set up on the ready to configure the toolkit and package. 1. Create a directory in the cmcluster (e.g., /etc/cmcluster/pkg/MySQL1). shared directory storage, you are for each package 2. Copy the toolkit files from /opt/cmcluster/toolkit/mysql to the package directory (/etc/cmcluster/pkg/MySQL1), and change directory to the package directory. 3. Configure hamysql.
PAGE 12
having the instance to migrate to standby node. procedure should be followed during maintenance: The following 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 as shown below: file /etc/cmcluster/pkg/MySQL1/mysql.debug $ touch /etc/cmcluster/pkg/MySQL1/mysql.
PAGE 13
Note: This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set to "yes" in the MySQL toolkit configuration file. G. Do and Don't with MySQL Toolkit Each of the Toolkits are designed with few assumptions that integrate with the respective application and with HP Serviceguard. It is recommended to follow the below mentioned guidelines for setting up the Package using MySQL Toolkit. A. DOs ---1.
PAGE 14
to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.