Removing Oracle Solaris ZFS Snapshot Application Resource Groups

Language:

To make an application highly available, the application must be managed as a resource in an application resource group. This section contains information about removing an application resource group from an Oracle Solaris ZFS snapshot protection group.

How to Remove an Application Resource Group From an Oracle Solaris ZFS Snapshot Protection Group

In disaster recovery framework ZFS snapshot replication feature, application resource group in a protection group is closely bound to the replication components that is associated to the application resource group. You must remove the application resource group and its associated replication component to completely remove the application resource group from the protection group's control. You could remove the replication component first and then the application resource group, or vice versa.

Note that you can remove any such configuration from the protection group only when the protection group is deactivated, which in turn implies that the application resource group is in unmanaged state.

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, click the partnership name, click the protection group name, highlight the resource group name, and click Remove. 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.

Before You Begin

Ensure that the following conditions are met:

The protection group is defined on the local cluster.
The resource group to be removed is part of the application resource groups of the protection group.
The protection group is deactivated on both partner clusters.

Assume the root role or assume a role that is assigned the Geo Management RBAC rights profile.
For more information about RBAC, 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 RBAC 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 RBAC rights profile and Oracle Solaris ZFS snapshot software.
Remove the application resource group from the protection group.
Type the following command in one node of the local partner cluster.
```
# geopg remove-resource-group application-resource-group protection-group
```
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.

The command removes an application resource group from a protection group on the local cluster. If the partner cluster contains a protection group of the same name, the command also removes the application resource group from the protection group on the partner cluster.
If one or more replication components associated with the application still exists in the protection group, remove such replication components as described in How to Remove a Replication Component From an Oracle Solaris ZFS Snapshot Protection Group.

Example 2 Removing an Oracle Solaris ZFS Snapshot Application Resource Group From a Protection Group

The following example removes two application resource groups, apprg1 and apprg2, from the zfssnap-pg protection group.

# geopg remove-resource-group apprg1,apprg2 zfssnap-pg

Troubleshooting

If the remove 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 remove operation is unsuccessful on the partner cluster, the configuration status is set to Error on the partner cluster.