How to Deactivate a Protection Group

Language:

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, click the partnership name to go to its page, highlight the protection group name, and click Stop Protection Group. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Administering an Oracle Solaris Cluster 4.4 Configuration.

You can deactivate, or stop, a protection group in the following ways:

Globally, meaning you deactivate a protection group on both the primary and the standby cluster where the protection group is configured
On the primary cluster only
On the standby cluster only

This procedure deactivates the protection group on all nodes of the primary and secondary clusters, depending on the scope of the command. When you deactivate a protection group, its application resource groups are also unmanaged.

The result of deactivating a protection group on the primary or standby cluster depends on the type of data replication that you are using.

If you are using Oracle Data Guard software, you can stop the Oracle Data Guard configuration from the primary or the standby cluster when the configuration is enabled because the Oracle Data Guard command-line interface (dgmgrl) on both clusters still accepts commands.

Assume the root role or assume a role that is assigned the Geo Management rights profile.
For more information, see Disaster Recovery Framework Rights Profiles 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 data replication software.
Deactivate the protection group.
When you deactivate a protection group on the primary cluster, its application resource groups are also taken offline.
```
# geopg stop -e scope [-D] protection-group-name
```
–e scope

Specifies the scope of the command.

If the scope is Local, then the command operates on the local cluster only. If the scope is Global, the command operates on both clusters where the protection group is deployed.

Note - The property values, such as global and local, are not case sensitive.

–D

Specifies that only replication should be stopped and the protection group should be online.

If you omit this option, the replication subsystem and the protection group are both stopped. If the role of the protection group on the local cluster is primary, omitting the –D option also results in taking the application resource groups offline and putting them in an unmanaged state.

protection-group-name

Specifies the name of the protection group.

The following data replication products have additional behaviors:
- For Oracle Data Guard, if the role of the protection group is primary on the local cluster, the geopg stop command disables the Oracle Data Guard Broker configuration.
  - If the geopg stop command fails, run the geoadm status command or Oracle Solaris Cluster Manager to see the status of each data replication component. For example, the Configuration status might be set to Error depending on the cause of the failure. The protection group might remain activated even though some resource groups might be unmanaged. The protection group might be deactivated with data replication running.
  - If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate a Protection Group in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

Example 22 Deactivating a Protection Group on All Clusters

This example deactivates a protection group on all clusters.

# geopg stop -e global sales-pg

Example 23 Deactivating a Protection Group on the Local Cluster

This example deactivates a protection group on the local cluster.

# geopg stop -e local sales-pg

Example 24 Stopping Remote Replication While Leaving the Protection Group Online

This example stops replication on the local cluster only.

# geopg stop -e local -D sales-pg

If you decide later to deactivate both the protection group and its underlying replication subsystem, you can rerun the command without the –D option:

# geopg stop -e local sales-pg

Example 25 Deactivating a Protection Group While Keeping Application Resource Groups Online

This example keeps online two application resource groups, apprg1 and apprg2, while deactivating their protection group, sales-pg, on both clusters.

Remove the application resource groups from the protection group.
```
# geopg remove-resource-group apprg1,apprg2 sales-pg
```
Deactivate the protection group.
```
# geopg stop -e global sales-pg
```

Troubleshooting

If the geopg stop command fails, run the geoadm status command or Oracle Solaris Cluster Manager to obtain the status of each data replication component. For example, the configuration status might be set to Error depending on the cause of the failure. The protection group might remain activated even though some resource groups might be unmanaged. The protection group might be deactivated with replication running.

If the configuration status is set to Error, revalidate the protection group. See Validating a Protection Group in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.