To make an application highly available, the application must be managed as a resource in an application resource group.
Perform this procedure to add an existing application resource group to the list of application resource groups in a protection group. At protection group creation time, if you specified application resource groups in the goldengate_geo_config configuration file and executed the goldengate_geo_register script, such application resource groups were added to the protection group.
All of the entities that you configure for the application resource group on the primary cluster, such as application data resources, application configuration files, and resource groups, must be replicated manually on the secondary cluster. The resource group names must be identical on both clusters. Also, the data that the application resource uses must be replicated on the secondary cluster.
You can add an existing application resource group to the list of application resource groups in 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. In the case where the entire cluster is rebooted, once the Geographic Edition software starts 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 replication component defined by the resource must contain the same entries in identical order as the Nodelist property of the protection group.
If the application resource group must have dependencies on resource groups and resources that are not managed by this protection group, ensure that the External_dependencies_allowed property of the protection group is set to TRUE.
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 Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide .
# clresourcegroup show -p Auto_start_on_new_cluster resource-group
If necessary, change the property to False.
# clresourcegroup set -p Auto_start_on_new_cluster=False resource-group
# geopg show protection-group | grep -i external_dependency_allowed
If necessary, change the property value to True.
# geopg set-prop -p External_dependency_allowed=TRUE protection-group
Geographic Edition requires that the application resource group be in an unmanaged state on the secondary cluster. If the protection group is stoped on the primary cluster, the application resource group must be unmanaged on the primary cluster also. If the protection group is active on the primary cluster, the application resource group must be in an unmanaged or in an online state on the primary cluster.
# geopg add-resource-group application-resource-group protection-group
In this syntax, application-resource-group specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list. In addition, 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, if the partner cluster contains a protection group of the same name, the command propagates the new configuration information to the partner cluster.
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, in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide .
After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. The application resource group is now affected by protection group operations such as start, stop, switchover, and takeover.
In the following example, the application resource groups apprg1 and apprg2, are added to the goldengate-pg protection group.
# geopg add-resource-group apprg1,apprg2 goldengate-pg