Adding an Application Resource Group to an Oracle ZFS Storage Appliance Protection Group

Language:

To make an application highly available, the application must be managed as a resource in an application resource group.

The initial registration of the protection group is performed with the zfssa_geo_register script. This section explains how to manage the application resource groups on their own.

All the entities you configure for the application resource group on the primary cluster, such as application data resources, application configuration files, and the 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.

How to Add an Application Resource Group to an Oracle ZFS Storage Appliance Protection Group

Perform this procedure to add an existing resource group to the list of application resource groups for a protection group.

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name, click the protection group name, and in the Resource Groups section click Add Resource Groups. For more information about Oracle Solaris Cluster Manager, see Chapter 12, Using the Oracle Solaris Cluster Manager Browser Interface in Administering an Oracle Solaris Cluster 4.4 Configuration.

Note - When the protection is initially created, any resource groups that are specified in the zfssa_geo_config configuration file are automatically created as well. Thus, you do not need to perform this procedure to add the resource groups specified in the zfssa_geo_config file at the time the protection group was created.

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, 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.

Before You Begin

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.

Assume the root role or assume a role that is assigned the Geo Management rights profile.
For more information, see Securing Disaster Recovery Framework Software in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
Note - If you use a role with Geo Management rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, assume the root role 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 rights profile and Oracle ZFS Storage Appliance software.

Ensure that the Auto_start_on_new_cluster property of the resource group is set to False.

# clresourcegroup show -p Auto_start_on_new_cluster resource-group

If necessary, change the property value to False.

# clresourcegroup set -p Auto_start_on_new_cluster=False resource-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.
```
# geopg list protection-group | grep -i external_dependencies_allowed
```
If necessary, change the property value to True.
```
# geopg set-prop -p External_dependencies_allowed=TRUE protection-group
```
(Optional) If the protection group is offline, take offline the application resource group.
If the protection group is offline, the application resource group must also be offline before it can successfully be added to the protection group.
```
# clresourcegroup offline resource-group
```
Add an application resource group to the protection group.
```
# geopg add-resource-group application-resource-group protection-group [-p external_dependencies_allowed=TRUE]
```
application-resource-group

Specifies the name of an application resource group. You can specify more than one resource group in a comma-separated list.

protection-group

Specifies the name of the protection group.

-p external_dependencies_allowed=TRUE

Permits the application resource group to have dependencies on resource groups and resources that are outside of the protection group.

The 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 the disaster recovery framework, see Appendix B, Legal Names and Values of Disaster Recovery Framework Entities, in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

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.
If necessary, bring online the application resource group.
```
# clresourcegroup online application-resource-group
```

Example 1 Adding an Application Resource Group to an Oracle ZFS Storage Appliance Protection Group

The following example adds two application resource groups, apprg1 and apprg2, to the zfssa-pg protection group.

# geopg add-resource-group apprg1,apprg2 zfssa-pg

Troubleshooting

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.