Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Resynchronizing a MySQL Protection Group

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 status`command 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 updates only entities that are related to Geographic Edition. To update Oracle Solaris Cluster resource groups, resource types, and resources, use the `cluster export -t rg,rt,rs` command to generate an XML cluster configuration file, modify the XML file for the expected configuration on the secondary cluster, and run the `clresource create` command with the `-a` option to apply the configuration updates. For more information, see How to Configure Oracle Solaris Cluster Software on All Nodes (XML) in Oracle Solaris Cluster Software Installation Guide and the `cluster`(1CL)and `clresource`(1CL) man pages.

The protection group must be deactivated on the cluster where you intend to run the `geopg update`command.

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

Copyright © 2004, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |