JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

Overview of MySQL Replication

MySQL Database Resource Group

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

Data Replication Layer Process for Validating the Application Resource Groups and Data Replication Entities

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

G.  Error Return Codes for Script-Based Plug-Ins


Administering MySQL Protection Groups

A MySQL protection group must cover at least one MySQL database per cluster. It cannot protect anything other than MySQL databases. So, if your partnership contains additional replication protocols, you must create separate protection groups for them.

Planning for Your MySQL Protection Group

A MySQL database resource group can belong to only one protection group.

The MySQL geographic replication was developed with the script-based plug-in module of Geographic Edition, so it must comply with all rules of the script-based plug-in. For each protection group, you must provide a script-based plug-in configuration file on each node. In addition, the MySQL geographic replication brings in its own configuration file, which is needed only at registration.

The MySQL geographic replication creation is an automated process that takes the MySQL geographic configuration file as input and performs the necessary actions. The essential content of this file consists of key=value pairs.

Explanation of Value
Name of the partnership.
Name of the protection group to create.
Name of the replicated component to create in this protection group.
Name of the replication resource.
Name of the replication resource group.
Description for the protection group.
Absolute path for the script-based plug-in configuration file.
Resource group names that contain the MySQL database resource on the clusters. If the resource group names on the clusters differ, provide a comma-separated list.
Resource names configured as the master and slave MySQL database resources. If the resource names on the clusters differ, provide a comma-separated list.
Switch for setting the read-only variable on the MySQL slave. If the read-only variable should not be set, leave this value undefined. Any entry here triggers the read-only variable to be set.
Application resource group, which is unmanaged and contains at least the logical host for client access.
Timeout for the extensive ping test. The default is 60 seconds if this variable is unset. This timeout is used at check_takeover where it must be verified as the remote site is unavailable.
Timeout for the short ping test. The default is 10 seconds if this variable is unset. The short ping timeout is used whenever a connection should succeed but is not required to succeed.