How to Add an Application Resource Group to a MySQL Protection Group

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.

1. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC.

   ---

   Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

   # chmod A+user:username:rwx:allow /var/cluster/geo

   The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

   ---

2. Add an application resource group to the protection group.

    # 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