Serviceguard Toolkits for Contrib User Guide Version A.12.00.00

1. Create a unique volume group and filesystem on shared storage for each instance of the
database to be included in the configuration.
2. On each node, create a mount point for each filesystem. The mount point for a specified
instance/package must be the same for all the nodes.
The following example shows a configuration of MySQL for a filesystem, /MySQL_1 on /dev/
vg01.
1. Assuming that LVM is set up on the shared storage, create a filesystem (for example, /MySQL_1)
on the LV and mount point (for example, /MySQL_1) on each of the nodes to mount the
filesystem.
2. Create the database on the lvol in /MySQL_1.
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.
Changes may include specific assignments to the following parameters:
[mysqld]
* datadir=/MySQL_1/mysql
* socket=/MySQL_1/mysql/mysql.sock
* port= <UNIQUE PORT NUMBER>
[mysqld_safe]
* err-log=/MySQL_1/mysql/mysqld.err
* pid-file=$SGCONF/pkg/mysql1/mysqld.pid
NOTE:
• Since each database instance resides in its own filesystem, multiple database instances can
be configured in the environment using this method.
• In the case of MySQL version for SLES, mysqld_safe is known as safe_mysqld. Hence,
you have to modify the suitable sections in the my.cnf file.
• The mysqld_multi feature of MySQL is not supported with MySQL toolkit on SLES and Redhat
systems. Use separate MySQL toolkit packages for each instance of MySQL.
Supported Configuration
This section explains the following supported configurations for MySQL toolkit packages:
• Local configuration
• Shared configuration
• Multiple instance configuration
NOTE:
• Each node must have the same version of the MySQL application.
• Each node must have the same configuration directory where identical copies of the
configuration files for each instance are placed in the local or shared hard disk.
• Each node must have the same file system directories to access the same shared storage.
Local configuration
In a typical local configuration, files are not shared among the nodes. If you opt to store the
configuration files on a local disk, you must replicate the configuration to local disks on all the
nodes configured to run the package. Identical copies of the MySQL server configuration file must
reside in exactly the same locations on each node. If you update the information in a file on a
single node, you must update the files on all the other nodes with the same changes. Ensure that
all the files on all the nodes are identical and always up-to-date.
Supported Configuration 15