This section provides guidelines and instructions to deactivate a protection group.
The result of deactivating a protection group on the primary or standby cluster depends on the type of data replication that you are using.
Data replication can be stopped only from the primary cluster. So, when you deactivate a protection group on the secondary cluster, this deactivate command does not stop data replication.
If the role of the protection group is Primary on the local cluster, the geopg stop command disables the autosynchronization of each device group and places the volume sets into logging mode.
The data replication configuration of the protection group is validated. During validation, the current local role of the protection group is compared with the aggregate device group state. If validation is successful, data replication is stopped.
Data replication is stopped on the data replication device groups that are configured for the protection group, whether the deactivation occurs on a primary or secondary cluster.
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.
If the role of the protection group is Primary on the local cluster, the geopg stop command disables the Oracle Data Guard Broker configuration.
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.
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
Before You Begin
Review the guidelines in Deactivating a Protection Group.
If you use a role with Geo Management rights, ensure that the /var/cluster/geo access control lists (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 ACL applied for compatibility between the Geo Management rights profile and data replication software.
For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
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
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.
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.
Specifies the name of the protection group.
This example deactivates a protection group on all clusters.
# geopg stop -e global sales-pgExample 21 Deactivating a Protection Group on the Local Cluster
This example deactivates a protection group on the local cluster.
# geopg stop -e local sales-pgExample 22 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-pgExample 23 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 Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.