Oracle® Solaris Cluster Geographic Edition System Administration Guide

Exit Print View

Updated: July 2014, E39667-01

How to Delete a Protection Group

Use the following procedure to delete a protection group from the local cluster.

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name to go to its page, then in the Protection Groups section highlight the protection group name and click Delete. For more information about Oracle Solaris Cluster Manager, see Chapter 13, Using the Oracle Solaris Cluster GUI, in Oracle Solaris Cluster System Administration Guide .

If you want to delete the protection group everywhere, you must run the geopg delete command on each cluster where the protection group exists.

To keep the application resource groups online while deleting the protection group, you must remove the application resource groups from the protection group. See Example 7–9 for examples of this procedure.

Before You Begin

Ensure that the following conditions are met:

  • The protection group you want to delete exists locally.

  • The protection group is offline on all clusters from which you want to delete it.

  1. Log in to one of the nodes on the primary cluster, cluster-paris.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .

  2. Delete the protection group.

    the following command deletes the configuration of the protection group from the local cluster. The command also removes the replication resource group for each device group in the protection group.

    # geopg delete protection-group-name 

    Specifies the name of the protection group

  3. To also delete the protection group on the secondary cluster, repeat Step 1 and Step 2 from a node of the secondary cluster.
Example 7-8  Deleting a Protection Group

This example deletes a protection group srdfpg from both partner clusters. The protection group is offline on both partner clusters.

In this example, phys-paris-1 is a node of the primary cluster and phys-newyork-1 is a node of the secondary cluster.

# rlogin phys-paris-1 -l root
phys-paris-1# geopg delete srdfpg
# rlogin phys-newyork-1 -l root
phys-newyork-1# geopg delete srdfpg
Example 7-9  Deleting an EMC SRDF Protection Group While Keeping Application Resource Groups Online

This example keeps online two application resource groups, apprg1 and apprg2, while deleting their protection group, srdfpg, from both partner clusters. The following commands remove the application resource groups from the protection group, then delete the protection group.

phys-paris-1# geopg remove-resource-group apprg1,apprg2 srdfpg
phys-paris-1# geopg stop -e global srdfpg
phys-paris-1# geopg delete srdfpg
phys-newyork-1# geopg delete srdfpg


If the deletion is unsuccessful, the configuration status is set to Error. Fix the cause of the error and rerun the geopg delete command.

For Oracle Data Guard, unlike other data replication modules, the Oracle database-server resource group is not added to the protection group. Instead, a shadow Oracle database-server resource group is added to represent this resource group. You can add and remove the shadow Oracle database-server resource group to and from the protection group at any time without affecting the Oracle Data Guard data replication. Consequently, the application resource groups that are shown in this example would have no data to replicate in an Oracle Data Guard protection group. Application resource groups that might meet this criteria can be scalable web servers, where their data is static or held on some remote storage that is not controlled by this cluster.