Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 4.1 |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
4. Administering Access and Security
5. Administering Cluster Partnerships
7. Administering Protection Groups
8. Monitoring and Validating the Geographic Edition Software
9. Customizing Switchover and Takeover Actions
A. Standard Geographic Edition Properties
B. Legal Names and Values of Geographic Edition Entities
C. Disaster Recovery Administration Example
E. Troubleshooting Geographic Edition Software
F. Deployment Example: Replicating Data With MySQL
MySQL Replication Resource Group
MySQL Application Resource Group
Initial Configuration of MySQL Replication
Installing MySQL and Configuring the MySQL Database Resource Group
How to Configure the MySQL Replication
Configuring the MySQL Application Resource Group
Administering MySQL Protection Groups
Planning for Your MySQL Protection Group
Creating, Modifying, Validating, and Deleting a MySQL Protection Group
How to Create the MySQL Configuration
Modifying a MySQL Protection Group
Validating a MySQL Protection Group
How to Delete a MySQL Protection Group
Administering MySQL Application Resource Groups
How to Add an Application Resource Group to a MySQL Protection Group
How to Delete an Application Resource Group From a MySQL Protection Group
Administering MySQL Data-Replicated Components
How to Add a Data-Replicated Component to a MySQL Protection Group
Data Replication Subsystem Process for Verifying the Replicated Component
How to Modify a MySQL Data-Replicated Component
How to Delete a Data-Replicated Component From a MySQL Protection Group
Replicating a MySQL Protection Group Configuration to a Partner Cluster
Activating and Deactivating a MySQL Protection Group
Activating a MySQL Protection Group
Deactivating a MySQL Protection Group
Resynchronizing a MySQL Protection Group
Recovery Strategy After a Takeover of a MySQL Protection Group
How to Recover After a Takeover
Performing the initial configuration consists of the following tasks:
Installing MySQL and configuring the MySQL database resource group
Configuring the MySQL replication
Configuring the MySQL application resource group
This section contains the following information:
You can install MySQL and configure both clusters as described in Oracle Solaris Cluster Data Service for MySQL Guide.
The database resource group and its resources do not have to have the same name on both clusters.
Requirements for Geographic Edition controlling MySQL are as follows:
Do not use the bind-address keyword in the MySQL configuration file my.cnf.
Specify the nodes of all clusters in the mysql_config file for database preparation.
When preparing the MySQL database for cluster usage with the mysql_register script, you must provide all the physical node names or zone names of your clusters in the variable: MYSQL_NIC_HOSTNAME. For example:
MYSQL_NIC_HOSTNAME="cl1-phys1,cl1,phys2,cl2-phys3,cl2-phys4"
When you are configuring the database resource, keep the following restrictions in mind :
The configuration of the MySQL database resource as a Service Management Facility (SMF) component on top of a failover container resource is not allowed.
The MySQL replication between the two clusters must be the only MySQL replication configured in the two databases.
The MySQL databases on both clusters must be configured to listen on the same port.