You can add an existing resource group to the list of application resource groups for a protection group. 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 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 command.
# clresourcegroup show -p auto_start_on_new_cluster apprg
When you bring a protection group online on the primary cluster, you should 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 Sun Cluster resource group manager from automatically starting the application resource groups. In this case, the start up of resource groups is reserved to the Sun Cluster Geographic Edition software.
Application resource groups should be online only on the primary cluster when the protection group is activated.
Set the Auto_start_on_new_cluster property to False as follows:
# clresourcegroup set -p Auto_start_on_new_cluster=False apprg
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 the application resource groups to the protection group in a single operation. If you add the application resource groups separately, the operation fails.
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 Active after the configuration of the protection group has changed, the local state of the protection group becomes Degraded.
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 active resource group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Add an application resource group to 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 of the same name.
# geopg add-resource-group resourcegrouplist protectiongroup
Specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
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.
This example adds two application resource groups, apprg1 and apprg2, to tcpg.
# geopg add-resource-group apprg1,apprg2 tcpg