Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide |
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
Recovery Strategy After a Takeover of a MySQL Protection Group
How to Recover After a Takeover
You can resynchronize the configuration information for the local protection group with the configuration information retrieved from the partner cluster. You need to resynchronize a protection group when its synchronization status in the output of the geoadm statuscommand is Error.
For example, you might need to resynchronize protection groups after booting the cluster. For more information, see Booting a Cluster.
Resynchronizing a protection group only updates entities that are related to Geographic Edition. For more information, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Oracle Solaris Cluster Data Services Planning and Administration Guide
The protection group must be deactivated on the cluster where you intend to run the geopg updatecommand.
Use the following command to resynchronize the protection group.
# geopg update protection-group
In this syntax, protection-group specifies the name of the protection group.
Example F-14 Resynchronizing a MySQL Protection Group
In the following example, a protection group is resynchronized:
# geopg update mysql-pg