HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index
cmmodpkg -e -n node1 -n node2 mysql_1
cmmodpkg -e mysql_1
11. If the package does not start, to start the package run the cmrunpkg command.
cmrunpkg mysql_1
Repeat these procedures to create multiple MySQL instances running in the Serviceguard
environment.
Database Maintenance
At regular intervals, the MySQL database needs maintenance like changing configuration, without
migrating the instance to migrate to standby node. Follow the procedure during database
maintenance:
NOTE: 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 the 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 (For example, changing the configuration parameters in the
parameter file of the MySQL instance. If this file is changed, 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
96 Using MySQL Toolkit in a HP Serviceguard Cluster