|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 4.1|
A protection group is the container for the application resource groups, which contain data for services that are protected from disaster. The Geographic Edition software protects the data by replicating it from the primary cluster to the secondary cluster. By adding a data-replicated component to a protection group, the software monitors the replication status of a MySQL database. The software also controls the role and state of the database during protection group operations such as start, stop, switchover, and takeover.
Before You Begin
Before you add a replication component to a protection group, ensure that the following conditions are met:
The protection group is defined on the local cluster.
The protection group is offline on the local cluster and the partner cluster, if the partner cluster can be reached.
The underlying MySQL database resources exist on both the local cluster and the partner cluster.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information, see Geographic Edition Software and RBAC.
The following command adds a replication component to a protection group on the local cluster and propagates the new configuration to the partner cluster if the partner cluster contains a protection group with the same name.
# geopg add-replication-component -p property [-p...] MySQL-replicated-component protection-group
In this syntax, -p property specifies the properties of the data-replicated component group. You can specify the following script-based plug-in properties:
switchover_args — Specifies the command-line arguments for the switchover script
takeover_args — Specifies the command-line arguments for the takeover script
start_replication_args — Specifies the command-line arguments for the start_replication script
remove_config_args — Specifies the command-line arguments for the remove_configuration script
create_config_args — Specifies the command-line arguments for the create_configuration script
stop_replication_args — Specifies the command-line arguments for the stop_replication script
Caution - Make sure that the command-line arguments are the same for all scripts.
For more information about the properties you can set, see Property Descriptions for Script-Based Plug-Ins.
Also in this syntax, MySQL-replicated-component specifies the name of the new data-replicated component, and protection-group specifies the name of the protection group that will contain the new data-replicated component.
For information about the names and values that are supported, see Appendix B, Legal Names and Values of Geographic Edition Entities.
For more information about the geopg command, refer to the geopg(1M) man page.
Note - Because the add operation for the replication component is performed during the scripted registration, an example is not provided here.
During protection group validation, the MySQL data replication layer validates the application resource groups and the data replication entities by verifying that an application resource group in the protection group has its Auto_start_on_new_cluster property set to false.
When you bring a protection group online on the primary cluster, bring the application resources groups participating in that protection group online only on the same primary cluster. Setting the Auto_start_on_new_cluster property to false prevents the Oracle Solaris Cluster resource group manager from automatically starting the application resource groups. In this case, the startup of resource groups is reserved for the Geographic Edition software.
Application resource groups should be online only on the primary cluster when the protection group is activated.
The Mysql geocontrol module supplies a script that is used by the script-based plug-in module. The script entry points require the same set of arguments. These arguments are validated for semantics and completeness. The following validation checks are performed:
Are all of the mandatory arguments defined?
Is the configured MySQL database resource defined?
Is the specified replication resource configured with a correct start command, if the resource exists already?
Are the long and short ping intervals numeric?
When the validation is complete, the Geographic Edition software adds the application resource group to the protection group.
Note - Every entry point of the underlying script-based plug-in has a validation method. In the case of the MySQL replication, all the validation methods are the same.