test

Sun Cluster Data Service for MySQL Guide for Solaris OS

Installing and Configuring Sun Cluster HA for MySQL

Installing and Configuring Sun Cluster HA for MySQL

Table 1–1 lists the tasks for installing and configuring Sun Cluster HA for MySQL. Perform these tasks in the order that they are listed.

Table 1–1 Task Map: Installing and Configuring Sun Cluster HA for MySQL

Task 

For Instructions, Go To 

1. Plan the installation. 

Sun Cluster HA for MySQL Overview

Planning the Sun Cluster HA for MySQL Installation and Configuration

2. Install and configure MySQL. 

How to Install and Configure MySQL

3. Verify installation and configuration. 

How to Verify the Installation and Configuration of MySQL

4. Install Sun Cluster HA for MySQL Packages. 

How to Install the Sun Cluster HA for MySQL Packages Using the scsintall Utility

5. Register and Configure Sun Cluster HA for MySQL. 

How to Register and Configure Sun Cluster HA for MySQL as a Failover Service

6. Verify Sun Cluster HA for MySQL Installation and Configuration. 

How to Verify the Sun Cluster HA for MySQL Installation and Configuration

7. Understand Sun Cluster HA for MySQL fault monitor. 

Understanding the Sun Cluster HA for MySQL Fault Monitor

8. Debug Sun Cluster HA for MySQL. 

Debug Sun Cluster HA for MySQL

9. Upgrade to SC3.1 when using Sun Cluster HA for MySQL. 

Upgrade to SC3.1 when Using Sun Cluster HA for MySQL

10. Upgrade to MySQL 4.0.15 from 3.23.54 when using Sun Cluster HA for MySQL. 

Upgrade to MySQL 4.0.x from 3.23.54 when using Sun Cluster HA for MySQL

Sun Cluster HA for MySQL Overview

The MySQL software delivers a fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.MySQL is a trademark of MySQL ABTM.

MySQL is freely available under the GNU General Public License, and you can downloaded it from http://www.mysql.com.

The Sun Cluster HA for MySQL data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover of the MySQL service. The following MySQL components are protected by the Sun Cluster HA for MySQL data service.

Table 1–2 Protection of Components

Component 

Protected by 

MySQL server 

Sun Cluster HA for MySQL  

Planning the Sun Cluster HA for MySQL Installation and Configuration

This section contains the information you need to plan your Sun Cluster HA for MySQL installation and configuration.

Configuration Restrictions

This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for MySQL only.

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

Caution – Caution –

Your data service configuration might not be supported if you do not observe these restrictions.

Configuration Requirements

The requirements in this section apply to Sun Cluster HA for MySQL only. You must meet these requirements before you proceed with your Sun Cluster HA for MySQL installation and configuration.

Caution – Caution –

Your data service configuration might not be supported if you do not adhere to these requirements.

Installing and Configuring MySQL

This section contains the procedures you need to install and configure MySQL.

References will be made to certain directories for MySQL. The following list shows common pathnames for these references. Refer to Configuration Restrictions where these examples .

How to Install and Configure MySQL

  1. Determine how MySQL will be deployed in Sun Cluster –

    • Determine how many MySQL instances will be deployed.

    • Determine which Cluster File System will be used by each MySQL instance.

  2. Mount the MySQL Cluster File Systems –

    Note –

    If Failover File Systems will be used by the MySQL instance, you must mount these manually.

  3. Install MySQL onto all nodes within Sun Cluster

    It is recommended that MySQL be installed onto a Global File System. For a discussion of the advantages and disadvantages of installing the software on local versus cluster files systems, see “Determining the Location of the Application Binaries” in the Sun Cluster Data Services Installation and Configuration Guide.

    Download MySQL from http://www.mysql.com — If you intend to use local disks for the MySQL software, you will need to repeat this step on all nodes within Sun Cluster.

  4. Create a mysql-user and mysql-group for MySQL on all nodes in the cluster that will run MySQL

    Create an entry in /etc/group on all nodes with Sun Cluster.


    • # groupadd -g 1000 mysql

      Create an entry in /etc/passwd on all nodes within Sun Cluster. This user should have a locked password.


      # useradd -u 1000 -g 1000 -d /global/mysql -s /bin/sh mysql

  5. Change owner and group for MySQL binaries

    If MySQL binaries are on all nodes then repeat this step.


    # chown -R mysql:mysql /global/mysql

  6. Create your MySQL Database directory for your MySQL Instance(s). 


    # mkdir <MySQL Database directory>
#
    Note –

    Refer back to Configuration Restrictions for a description of the <MySQL Database directory> and to Installing and Configuring MySQL for a list of common pathnames.

    Shows one MySQL instance. MySQL has been installed from http://www.mysql.com in /global/mysql which is mounted as a Global File System. The MySQL Database Directory for the MySQL instance is /global/mysql-data.

    Example 1–4 Directories for MySQL instance


    # cd /global/mysql
#
# ls -l
-rw-r--r--   1 mysql    mysql      19106 Dec 10 14:52 COPYING
-rw-r--r--   1 mysql    mysql      28003 Dec 10 14:52 COPYING.LIB
-rw-r--r--   1 mysql    mysql      44577 Dec  5 10:37 ChangeLog
-rw-r--r--   1 mysql    mysql       6811 Dec 10 14:53 INSTALL-BINARY
-rw-r--r--   1 mysql    mysql       1976 Dec  5 10:37 README
drwxr-xr-x   2 mysql    mysql       1024 Dec 13 18:05 bin
-rwxr-xr-x   1 mysql    mysql        773 Dec 10 15:34 configure
drwxr-x---   3 mysql    mysql        512 Apr  3 12:23 data
drwxr-xr-x   2 mysql    mysql       1024 Dec 10 15:35 include
drwxr-xr-x   2 mysql    mysql        512 Dec 10 15:35 lib
drwxr-xr-x   2 mysql    mysql        512 Dec 10 15:35 man
-rw-r--r--   1 mysql    mysql    2582089 Dec 10 14:47 manual.html
-rw-r--r--   1 mysql    mysql    2239278 Dec 10 14:47 manual.txt
-rw-r--r--   1 mysql    mysql      94600 Dec 10 14:47 manual_toc.html
drwxr-xr-x   6 mysql    mysql        512 Dec 10 15:35 mysql-test
drwxr-xr-x   2 mysql    mysql        512 Dec 10 15:35 scripts
drwxr-xr-x   3 mysql    mysql        512 Dec 10 15:35 share
drwxr-xr-x   7 mysql    mysql       1024 Dec 10 15:35 sql-bench
drwxr-xr-x   2 mysql    mysql        512 Dec 10 15:35 support-files
drwxr-xr-x   2 mysql    mysql        512 Dec 10 15:35 tests
#

  7. Create the MySQL my.cnf file according to your requirements — The Sun Cluster HA for MySQL data service provides two sample my.cnf file for MySQL: one sample configuration file is for a master configuration and one sample file is for a slave configuration.

    Note –

    If the Sun Cluster HA for MySQL package (SUNWscmys) was not installed during your initial Sun Cluster installation, proceed to Installing the Sun Cluster HA for MySQL Packages to install it on SC3.1 and SC3.0U3. Return here to continue the Installation and Configuration of MySQL.

    The contents of /opt/SUNWscmys/etc/my.cnf_sample_[master|slave]provide a sample MySQL configuration file that you can use to create your MySQL instance <MySQL Databasedirectory>/my.cnf.You must still edit that file to reflect your configuration values.


    # cp /opt/SUNWscmys/etc/my.cnf_sample_master  \
 <MySQL Databasedirectory>/my.cnf

  8. Bootstrap MySQL instance — This will create the privilege tables db, host, user, tables_priv and columns_priv in the mysql database, as well as the func table.


    # cd <MySQL Basedirectory>


    # ./scripts/mysql_install_db  \
--datadir=<MySQL Database directory>

  9. Create a logfile directory in <MySQL Database Directory> 


    # mkdir <MySQL Database Directory>/logs

  10. Change owner and group for <MySQL Database Directory> 


    # chown -R mysql:mysql <MySQL Database Directory>

  11. Change filepermission for <MySQL Database Directory>/my.cnf 


    # chmod 644  <MySQL Database Directory>/my.cnf

Verifying the Installation and Configuration of MySQL

This section contains the procedure you need to verify the installation and configuration.

How to Verify the Installation and Configuration of MySQL

This procedure does not verify that your application is highly available because you have not yet installed your data service.

Note –

Before verifying the installation and configuration of MySQL, ensure that the Logical Hostname for the mysql is available. You will need to complete steps 2 through 7 in How to Register and Configure Sun Cluster HA for MySQL as a Failover Service.

  1. Start the MySQL Server for this instance.


    #cd <MySQL Basedirectory>


    # ./bin/mysqld --defaults-file=<MySQL Databasedirectry>/my.cnf \
--basedir=<MySQL Basedirectory>\
 --datadir=<MySQL Databasedirectory>\
 --user=mysql --pid-file=<MySQL Databasedirectory>/mysqld.pid &

  2. Connect to the MySQL instance.


    # <MySQL Basedirectory>/bin/mysql -h <Logical host> -uroot

  3. Stop the MySQL server instance.


    # kill -TERM `cat <MySQL Databasedirectory>/mysqld.pid

Installing the Sun Cluster HA for MySQL Packages

If you did not install the Sun Cluster HA for MySQL packages during your initial Sun Cluster installation, perform this procedure to install the packages. Perform this procedure on each cluster node where you are installing the Sun Cluster HA for MySQL packages. To complete this procedure, you need the Sun Java Enterprise System Accessory CD Volume 3.

If you are installing more than one data service simultaneously, perform the procedure in “Installing the Software” in Sun Cluster 3.1 10/03 Software Installation Guide.

Install the Sun Cluster HA for MySQL packages using one of the following installation tools:

Note –

The Web Start program is not available in releases earlier than Sun Cluster 3.1 Data Services 10/03.

How to Install the Sun Cluster HA for MySQL Packages by Using the Web Start Program

You can run the Web Start program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the Web Start program, see the installer(1M) man page.

Note –

If you are working at a machine that is remotely connected to the machine where the CD-ROM is loaded, be careful. If you intend to run the Web Start program with a GUI, ensure that your DISPLAY environment variable is set. Otherwise, the Web Start program runs with the CLI.

  1. Become superuse on the cluster node where you are installing the Sun Cluster HA for MySQL packages.

  2. Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

    If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

  3. Change to the Sun Cluster HA for MySQL component directory of the CD-ROM.

    The Web Start program for the Sun Cluster HA for MySQL data service resides in this directory.


    # cd /cdrom/cdrom0/components/SunCluster_HA_MySQL_3.1

  4. Start the Web Start program.


    # ./installer

  5. When you are prompted, select the type of installation.

    • To install only the C locale, select Typical.

    • To install other locales, select Custom.

  6. Follow instructions on the screen to install the Sun Cluster HA for MySQL packages on the node.

    After the installation is finished, the Web Start program provides an installation summary. This summary enables you to view logs that the Web Start program created during the installation. These logs are located in the /var/sadm/install/logs directory.

  7. Exit the Web Start program.

  8. Unload the Sun Java Enterprise System Accessory CD Volume 3 from the CD-ROM drive.

    1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.

    2. Eject the CD-ROM.


      # eject cdrom

How to Install the Sun Cluster HA for MySQL Packages Using the scsintall Utility

You need the Sun Cluster Agents CD-ROM to perform this procedure. This procedure assumes that you did not install the data service packages during your initial Sun Cluster installation.

If you installed the Sun Cluster HA for MySQL packages as part of your initial Sun Cluster installation, proceed to Registering and Configuring Sun Cluster HA for MySQL.

Perform this procedure on all nodes that can run Sun Cluster HA for MySQL data service.

  1. Load the Sun Cluster Agents CD-ROM into the CD-ROM drive.

  2. Run the scinstall utility with no options.

    This step starts the scinstall utility in interactive mode.

  3. Choose the menu option, Add Support for New Data Service to This Cluster Node.

    The scinstall utility prompts you for additional information.

  4. Provide the path to the Sun Cluster Agents CD-ROM.

    The utility refers to the CD as the “data services cd.”

  5. Specify the data service to install.

    The scinstall utility lists the data service that you selected and asks you to confirm your choice.

  6. Exit the scinstall utility.

  7. Unload the CD from the drive.

Registering and Configuring Sun Cluster HA for MySQL

This section contains the procedures you need to configure Sun Cluster HA for MySQL.

How to Register and Configure Sun Cluster HA for MySQL as a Failover Service

This procedure assumes that you installed the data service packages during your initial Sun Cluster installation.

If you did not install the Sun Cluster HA for MySQL packages as part of your initial Sun Cluster installation, go to How to Install the Sun Cluster HA for MySQL Packages Using the scsintall Utility.

  1. Become superuser on one of the nodes in the cluster that will host MySQL.

  2. Register the SUNW.gdsresource type.


    # scrgadm -a -t SUNW.gds

  3. Register the SUNW.HAStoragePlus resource type.


    # scrgadm -a -t SUNW.HAStoragePlus

  4. Create a failover resource group.


    # scrgadm -a -g MySQL-failover-resource-group

  5. Create a resource for the MySQL Disk Storage.


    # scrgadm -a -j MySQL-has-resource  \
-g MySQL-failover-resource-group   \
-t SUNW.HAStoragePlus  \
-x FilesystemMountPoints=MySQL- instance-mount-points

  6. Create a resource for the MySQL Logical Hostname.


    # scrgadm -a -L -j MySQL-lh-resource  \
-g MySQL-failover-resource-group  \
-l MySQL-logical-hostname

  7. Enable the failover resource group that now includes the MySQL Disk Storage and Logical Hostname resources.


    # scswitch -Z -g MySQL-failover-resource-group
    Note –

    Make sure that the resource group is enabled on the same node as what was used when mysql_install_db was executed.

  8. Start the MySQL Server instance manually.


    #cd <MySQL Basedirectory>


    # ./bin/mysqld --defaults-file=<MySQL Databasedirectry>/my.cnf \
--basedir=<MySQL. Basedirectory>\
 --datadir=<MySQL Databasedirectory>\
 --user=mysql\
 --pid-file=<MySQL Databasedirectory>/mysqld.pid &

  9. Configure the admin password for the adminuser.


    # <MySQL Databasedirectry>/bin/mysqladmin -S /tmp/<Logical host>.sock password 'admin password'

  10. Create faultmonitor-user and a test-database for the MySQL instance.


    # cd /opt/SUNWscmys/util

    Edit the mysql_config file and follow the comments within that file:


    # Where is mysql installed (BASEDIR)
MYSQL_BASE=

# Mysql admin-user for localhost (Should be root)
MYSQL_USER=

# Password for mysql admin user
MYSQL_PASSWD=

# Configured logicalhost
MYSQL_HOST=

# Specify a username for a faultmonitor user
FMUSER=

# Pick a password for that faultmonitor user
FMPASS=

# Socket name for mysqld ( Should be /tmp/<Logical host>.sock )
MYSQL_SOCK=

# FOR SC3.1 ONLY, Specify the physical hostname for the
# physical NIC that this logicalhostname belongs to for every node in th
e
# cluster this Resourcegroup can located on.
# IE: The logicalhost lh1 belongs to hme1 for physical-node phys-1 and
# hme3 for  physical-node phys-2. The hostname for hme1 is phys-1-hme1 a
nd
# for hme3 on phys-2 it is phys-2-hme3.
# IE: MYSQL_NIC_HOSTNAME="phys-1-hme1 phys-2-hme3"
MYSQL_NIC_HOSTNAME=""
    Note –

    The following is an example for MySQL instance on SC3.1.


    MYSQL_BASE=/global/mysql
MYSQL_USER=root
MYSQL_PASSWD=root
MYSQL_HOST=hahostix1
FMUSER=fmuser
FMPASS=fmuser
MYSQL_SOCK=/tmp/hahostix1.sock
MYSQL_NIC_HOSTNAME="clusterix1 clusterix2"
    Note –

    If SC3.0U3 is being used, omitt the MYSQL_NIC_HOSTNAME parameter.

    After editing mysql_config you must run the mysql_register script.


    # ./mysql_register

  11. Stop the MySQL Server instance manually.


    # kill -TERM `cat <MySQL Databasedirectry>/mysqld.pid

  12. Create and register MySQL as a failover data service.


    # cd /opt/SUNWscmys/util

    Edit the ha_mysql_config file and follow the comments within that file, i.e.


     These parameters can be customized in (key=value) form
#
#        RS - name of the resource for the application
#        RG - name of the resource group containing RS
#   BASEDIR - name of the Mysql bin directory
#   DATADIR - name of the Mysql Data directory
# MYSQLUSER - name of the user Mysql should be started with
#        LH - name of the LogicalHostname SC resource
#    FMUSER - name of the Mysql fault monitor user
#    FMPASS - name of the Mysql fault monitor user password
#    LOGDIR - name of the directory mysqld should store it's logfile.
#    CHECK  - should HA-MySQL check MyISAM index files before start YES/
NO.
#    HAS_RS - name of the MySQL HAStoragePlus SC resource
#

    The following is an example for MySQL instance.


    RS=mysql-res
RG=mysql-rg
BASEDIR=/global/mysql
DATADIR=/global/mysql-data
MYSQLUSER=mysql
LH=hahostix1
FMUSER=fmuser
FMPASS=fmuser
LOGDIR=/global/mysql-data/logs
CHECK=YES 
HAS_RS=mysql-has-res

  13. Enable each MySQL resource.

    Repeat this step for each MySQL instance, if multiple instances were created.


    # scstat -g
# scswitch -e -j MySQL-resource

  14. Add adminuser for accessing locally a MySQL instance with a MySQL Logicalhost.

    Note –

    If you want to access the MySQL instance only through the socket (localhost), omit this step.

    When bootstraping MySQL the command mysql_install_db will create two adminusers, one belonging to localhost and one belonging to the node on which mysql_install_db was executed.

    If SC3.0U3 is being used you should delete the root user belonging to the physical node and add a adminuser belonging to the logicalhost

    The following is an example for MySQL instance on SC3.0U3.


    # mysql -S /tmp/hahostix1.sock -uroot
mysql> use mysql;
mysql> DELETE FROM user where User='root' AND Host='clusterix1';
mysql> GRANT ALL ON *.* TO 'root'@'hahostix1' IDENTIFIED BY 'rootpasswd';
mysql> exit;

    If you are using SC3.1, add a adminuser for every physical-node in the cluster that will run this MySQL instance.

    Note –

    If the nodename and the hostname for the physical interface are different, use the hostname for the physical interface.

    The following is an example for MySQL instance on SC3.1.


    # mysql -S /tmp/hahostix1.sock -uroot
mysql> use mysql;
mysql> mysql> GRANT ALL ON *.* TO 'root'@'clusterix2' IDENTIFIED BY 'rootpasswd';
mysql> mysql> GRANT ALL ON *.* TO 'root'@'clusterix1' IDENTIFIED BY 'rootpasswd';
mysql> exit;
    Note –

    You have to manually add Grant_priv to the admin users. See MySQL Administration documentation.

Verifying the Sun Cluster HA for MySQL Installation and Configuration

This section contains the procedure you need to verify that you installed and configured your data service correctly.

How to Verify the Sun Cluster HA for MySQL Installation and Configuration

  1. Become superuser on one of the nodes in the cluster that will host MySQL.

  2. Ensure all the MySQL resources are online with scstat.


    # scstat

    For each MySQL resource that is not online, use the scswitch command as follows.


    # scswitch -e -j MySQL- resouce

  3. Run the scswitch command to switch the MySQL resource group to another cluster node, such as node2.


    # scswitch -z -g MySQL-failover-resource-group -h node2

Understanding the Sun Cluster HA for MySQL Fault Monitor

This section describes the Sun Cluster HA for MySQL fault monitor's probing algorithm or functionality, states the conditions, messages, and recovery actions associated with unsuccessful probing.

For conceptual information on fault monitors, see the Sun Cluster Concepts Guide.

Resource Properties

The Sun Cluster HA for MySQL fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.

Probing Algorithm and Functionality

Debug Sun Cluster HA for MySQL

How to turn on debug for Sun Cluster HA for MySQL

Use the information in this section to understand how to turn on debug for Sun Cluster HA for MySQL.

Sun Cluster HA for MySQL can be used by multiple MySQL instances. However, it is possible to turn on debug for all MySQL instances or for a particular MySQL instance.

Each MySQL component has a DEBUG file under /opt/SUNWscmys/etc, where xxx is a three character abbreviation for the respective MySQL component.

These files allow you to turn on debug for all MySQL instances or for a specific MySQL instance on a particular node with Sun Cluster. If you require debug to be turned on for Sun Cluster HA for MySQL across the whole Sun Cluster, you will need to repeat this step on all nodes within Sun Cluster.

  1. Edit /etc/syslog.conf

    Edit /etc/syslog.conf and change daemon.notice to daemon.debug 


    # grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                     operator
#

    Change the daemon.notice to daemon.debug and restart syslogd. The output below, from the command grep daemon /etc/syslog.conf, shows that daemon.debug has been set.


    # grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.debug;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                    operator
#
# pkill -1 syslogd
#

  2. Edit /opt/SUNWscmys/etc/config and change DEBUG= to DEBUG=ALL or DEBUG=resource 


    # cat /opt/SUNWscmys/etc/config
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# Usage:
#       DEBUG=<RESOURCE_NAME> or ALL
#
DEBUG=ALL
#
    Note –

    To turn off debug, reverse the steps above.

Upgrade to SC3.1 when Using Sun Cluster HA for MySQL

Use the information in this section to understand how to upgrade to SC3.1 when using Sun Cluster HA for MySQL.

Note –

This procedure will not describe how to upgrade to SC3.1. It includes only the steps to upgrade Sun Cluster HA for MySQL to SC3.1.

This procedure shows the steps how to upgrade Sun Cluster HA for MySQL to SC3.1.

  1. Shutdown Sun Cluster HA for MySQL resource with scswitch —n —j MySQL- resouce.


    # scswitch -n -j MySQL- resouce

  2. Upgrade the nodes to SC3.1 according to Sun Cluster documentation.

  3. Start the MySQL Server manually on SC3.1.


    #cd <MySQL Basedirectory>


    # ./bin/mysqld --defaults-file=<MySQL Databasedirectry>/my.cnf \
--basedir=<MySQL Basedirectory>\
 --datadir=<MySQL Databasedirectory>\
 --user=mysql\
 --pid-file=<MySQL Databasedirectory>/mysqld.pid &

  4. Access the MySQL instance from local node with the socket option.


    #<MySQL Basedirectory>
/bin/mysql -S <MySQL Socket> -uroot \
 -p<Adminpassword>\

    The following is an example for a MySQL instance.


    # mysql -s /tmp/hahostix1.sock -uroot -proot
mysql>

  5. Drop the Sun Cluster HA for MySQL test database sc3_test_database.


    # mysql -s /tmp/hahostix1.sock -uroot -proot
mysql> DROP DATABASE sc3_test_database;
Query OK, 0 rows affected (0.03 sec)

  6. Delete all entries in db-table in mysql-database that contain User='<MySQL Faultmonitor user>'.


    # mysql -s /tmp/hahostix1.sock -uroot -proot
mysql> use mysql;
Database changed
mysql> DELETE FROM db WHERE User='fmuser';
Query OK, 1 row affected (0.03 sec)

  7. Delete all entries in user-table in mysql-database that contain User='<MySQL Faultmonitor user>'.


    # mysql -s /tmp/hahostix1.sock -uroot -proot
mysql> use mysql;
Database changed
mysql> DELETE FROM user WHERE User='fmuser';
Query OK, 1 row affected (0.03 sec)

  8. Add faultmonitor-user and a test-database to MySQL.


    # cd /opt/SUNWscmys/util

    Edit the mysql_config file and follow the comments within that file:


    # Where is mysql installed (BASEDIR)
MYSQL_BASE=

# Mysql admin-user for localhost (Should be root)
MYSQL_USER=

# Password for mysql admin user
MYSQL_PASSWD=

# Configured logicalhost
MYSQL_HOST=

# Specify a username for a faultmonitor user
FMUSER=

# Pick a password for that faultmonitor user
FMPASS=

# Socket name for mysqld ( Should be /tmp/<Logical host>.sock )
MYSQL_SOCK=

# FOR SC3.1 ONLY, Specify the physical hostname for the
# physical NIC that this logicalhostname belongs to for every node in the
# cluster this Resourcegroup can located on.
# IE: The logicalhost lh1 belongs to hme1 for physical-node phys-1 and
# hme3 for  physical-node phys-2. The hostname for hme1 is phys-1-hme1 and
# for hme3 on phys-2 it is phys-2-hme3.
# IE: MYSQL_NIC_HOSTNAME="phys-1-hme1 phys-2-hme3"
MYSQL_NIC_HOSTNAME=""
    Note –

    The following is an example for MySQL instance on SC3.1.


    MYSQL_BASE=/global/mysql
MYSQL_USER=root
MYSQL_PASSWD=root
MYSQL_HOST=hahostix1
FMUSER=fmuser
FMPASS=fmuser
MYSQL_SOCK=/tmp/hahostix1.sock
MYSQL_NIC_HOSTNAME="clusterix1 clusterix2"

  9. After editing mysql_config, run the mysql_register script.


    # ./mysql_register

  10. Stop the MySQL Server manually.


    # kill -TERM `cat <MySQL Databasedirectry>/mysqld.pid

  11. Startup Sun Cluster HA for MySQL resource with scswitch —e —j MySQL- resouce 


    # scswitch -e -j MySQL- resouce

  12. Change sourceaddress for adminuser for accessing locally a MySQL instance with a MySQL Logicalhost.

    Note –

    If you want to access the MySQL instance only through the socket (localhost), omitt this step.

    When SC3.0U3 has been used, delete the root user belonging to the logicalhost and add an adminuser belonging to the physicalhost.

    Note –

    If the nodename and the hostname for the physical interface are different, use the hostname for the physical interface.

    The following is an example for MySQL instance on SC3.1.


    # mysql -S /tmp/hahostix1.sock -uroot
mysql> use mysql;
mysql> DELETE FROM user where User='root' AND Host='hahostix1';
mysql> GRANT ALL ON *.* TO 'root'@'clusterix1' IDENTIFIED BY 'rootpasswd';
mysql> GRANT ALL ON *.* TO 'root'@'clusterix2' IDENTIFIED BY 'rootpasswd';
mysql> exit;
    Note –

    You have to manually add the Grant_priv to the admin users, See MySQL Administration documentation.

Upgrade to MySQL 4.0.x from 3.23.54 when using Sun Cluster HA for MySQL

Use the information in this section to understand how to upgrade to 4.0.12 when using Sun Cluster HA for MySQL.

Note –

The procedure will not describe how to upgrade to 4.0.x. It includes only the steps to upgrade Sun Cluster HA for MySQL to 4.0.x. These steps assume that the new MySQL binaries is installed in the same place. If the new binaries is installed in a new directory, you must re-register the MySQL resource with new MySQL Basedir.

Procedure to upgrade to MySQL 4.0.x from 3.23.54

  1. Shutdown the Sun Cluster HA for MySQL with scswitch —n —j MySQL- resouce 


    # scswitch -n -j MySQL- resouce

  2. Install the new MySQL binaries, follow Step 3 and 4 in Section How to Install and Configure MySQL.

  3. Startup Sun Cluster HA for MySQL with scswitch —e —j MySQL- resouce.


    # scswitch -e -j MySQL- resouce

  4. Shutdown Sun Cluster HA for MySQL faultmonitor with scswitch —n –M —j MySQL- resouce.


    # scswitch -n -M -j MySQL- resouce

  5. Follow the MySQL Documentation to upgrade MySQL Database.

  6. Startup Sun Cluster HA for MySQL faultmonitor with scswitch —e –M —j MySQL- resouce.


    # scswitch -e -M -j MySQL- resouce