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 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
You can add an existing application resource group to the list of application resource groups for a protection group.
Before You Begin
Before you add an application resource group to a protection group, ensure that the following conditions are met:
The protection group is defined.
The resource group to be added already exists on both clusters and is in an appropriate state.
The Auto_start_on_new_cluster property of the resource group is set to false. You can view this property by using the clresourcegroup show command. For example:
# clresourcegroup show -p Auto_start_on_new_cluster apprg1
You can set the Auto_start_on_new_cluster property to false as follows:
# clresourcegroup set -p Auto_start_on_new_cluster=false apprg1
Setting the Auto_start_on_new_cluster property to false prevents the Oracle Solaris Cluster resource group manager from automatically starting the resource groups in the protection group. Once the Geographic Edition software restarts and communicates with the remote cluster to ensure that the remote cluster is running and that the remote cluster is the secondary cluster for that resource group, the software will not automatically start the resource group on the primary cluster.
Application resource groups should be online only on the primary cluster when the protection group is activated.
The Nodelist property of the failover application resource group that has affinities with a replicated component defined by the resource must contain the same entries in identical order as the Nodelist property of the protection group.
The application resource group must not have dependencies on resource groups and resources outside of this protection group. To add several application resource groups that share dependencies, you must add all the application resource groups that share dependencies to the protection group in a single operation. If you add the application resource groups separately, the operation will fail.
The protection group can be activated or deactivated, and the resource group can be either online or unmanaged. If the resource group is unmanaged and the protection group is activated after the configuration of the protection group has changed, then the local state of the protection group becomes Error. If the resource group to add is online, and the protection group is deactivated, the request is rejected. You must activate the protection group before adding an online resource group.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information, see Geographic Edition Software and RBAC.
# geopg add-resource-group resource-group-list protection-group
In this syntax, resource-group-list specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list. Also, protection-group specifies the name of the protection group.
This command adds an application resource group to a protection group on the local cluster. Then, the command propagates the new configuration information to the partner cluster if the partner cluster contains a protection group with the same name.
For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities.
If the add operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the configuration status is set to OK on the local cluster. If the configuration status is OK on the local cluster, but the add operation is unsuccessful on the partner cluster, the configuration status is set to Error on the partner cluster.
After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. Then, the application resource group is affected by protection group operations such as start, stop, switchover, and takeover.
Example F-4 Adding an Application Resource Group to a MySQL Protection Group
In the following example, two application resource groups, apprg1 and apprg2, are added to mysql-pg:
# geopg add-resource-group apprg1,apprg2 mysql-pg