Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition Data Replication Guide for EMC Symmetrix Remote Data Facility

Search Scope:

- This Document
- Entire Library

## Deactivating an SRDF Protection Group

You can deactivate a protection group on the following levels:

- Globally – Deactivates a protection group on both clusters where the protection group is configured.

- On the primary cluster only – Secondary cluster remains active.

- On the secondary cluster only – Primary cluster remains active.

Deactivating an SRDF protection group on a cluster has the following effect on the data replication layer:

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

Deactivating a protection group has the following effect on the application layer:

- When a protection group is deactivated on the primary cluster, all of the application resource groups configured for the protection group are stopped and unmanaged.

- When a protection group is deactivated on the secondary cluster, the resource groups on the secondary cluster are not affected. Application resource groups that are configured for the protection group might remain active on the primary cluster, depending on the activation state of the primary cluster.

The SRDF command that is used to stop data replication depends on the RDF state of the SRDF device group.

The following table describes the SRDF command that is used to stop data replication for each of the possible combinations of factors.

Table 2-3 Commands Used to Stop SRDF Data Replication

Aggregate Device Group State | Valid Local Protection Group Role | SRDF Command
--- | --- | ---
`Split`, `Suspended, Partitioned,` or `Failover` | `primary` or `secondary` | No command is run because no data is being replicated.
`Synchronized` or `R1Updated` | `primary` or `secondary` | The `symrdf split` command is run.

## How to Deactivate an SRDF Protection Group

1. Log in to a cluster node.

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

2. 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] protectiongroupname

   `-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 data replication should be stopped and the protection group should be online.

     If you omit this option, the data replication subsystem and the protection group are both stopped.

   protectiongroupname

     Specifies the name of the protection group.

Example 2-17 How the Geographic Edition Software Issues the Command to Stop Replication

This example illustrates how the Geographic Edition software determines the SRDF command that is used to stop data replication.

The current state of the SRDF device group, `devgroup1`, is returned in the output of the `symrdf query` command as follows:

    phys-paris-1# symrdf -g devgroup1 query
    Device Group (DG) Name             : devgroup1
    DG's Type                          : RDF1
    DG's Symmetrix ID                  : 000187401215

           Source (R1) View                 Target (R2) View     MODES
    --------------------------------    ------------------------ ----- ------------
                 ST                  LI      ST
    Standard      A                   N       A
    Logical       T  R1 Inv   R2 Inv  K       T  R1 Inv   R2 Inv       RDF Pair
    Device  Dev   E  Tracks   Tracks  S Dev   E  Tracks   Tracks MDA   STATE
    -------------------------------- -- ------------------------ ----- ------------

    DEV001  00E4 RW       0        0 RW 00E4 WD       0        0 S..   Synchronized
    DEV002  00E5 RW       0        0 RW 00E5 WD       0        0 S..   Synchronized
    DEV003  00E6 RW       0        0 RW 00E6 WD       0        0 S..   Synchronized
    DEV004  00E7 RW       0        0 RW 00E7 WD       0        0 S..   Synchronized
    DEV005  00E8 RW       0        0 RW 00E8 WD       0        0 S..   Synchronized
    DEV006  00E9 RW       0        0 RW 00E9 WD       0        0 S..   Synchronized

A device group, `devgroup1`, is added to the protection group as follows:

    phys-paris-1# geopg add-device-group -p DG_or_CG=DG devgroup1 srdfpg

Next, the protection group, `srdfpg`, is deactivated by using the `geopg stop` command.

    phys-paris-1# geopg stop -s local srdfpg

The Geographic Edition software runs the `symrdf -g devgroup1 split` command at the data replication level.

If the command is successful, the state of `devgroup1` is returned in the output of the `symrdf query` command as follows:

    phys-paris-1# symrdf -g devgroup1 query
    Device Group (DG) Name             : devgroup1
    DG's Type                          : RDF1
    DG's Symmetrix ID                  : 000187401215

           Source (R1) View                 Target (R2) View     MODES
    --------------------------------    ------------------------ ----- ------------
                 ST                  LI      ST
    Standard      A                   N       A
    Logical       T  R1 Inv   R2 Inv  K       T  R1 Inv   R2 Inv       RDF Pair
    Device  Dev   E  Tracks   Tracks  S Dev   E  Tracks   Tracks MDA   STATE
    -------------------------------- -- ------------------------ ----- ------------

    DEV001  00E4 RW       0        0 NR 00E4 RW       0        0 S..   Split
    DEV002  00E5 RW       0        0 NR 00E5 RW       0        0 S..   Split
    DEV003  00E6 RW       0        0 NR 00E6 RW       0        0 S..   Split
    DEV004  00E7 RW       0        0 NR 00E7 RW       0        0 S..   Split
    DEV005  00E8 RW       0        0 NR 00E8 RW       0        0 S..   Split
    DEV006  00E9 RW       0        0 NR 00E9 RW       0        0 S..   Split

Example 2-18 Deactivating a Protection Group on All Clusters

This example deactivates a protection group on all clusters.

    # geopg stop -e global srdfpg

Example 2-19 Deactivating a Protection Group on a Local Cluster

This example deactivates a protection group on the local cluster.

    # geopg stop -e local srdfpg

Example 2-20 Stopping Data Replication While Leaving the Protection Group Online

This example stops only data replication on both partner clusters.

    # geopg stop -e local -D srdfpg

If the administrator decides later to deactivate both the protection group and its underlying data replication subsystem, the administrator can rerun the command without the `-D` option:

    # geopg stop -e local srdfpg

Example 2-21 Deactivating an SRDF Protection Group While Keeping Application Resource Groups Online

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

1. Remove the application resource groups from the protection group.

       # geopg remove-resource-group apprg1,apprg2 srdfpg

2. Deactivate the protection group.

       # geopg stop -e global srdfpg

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |