Creating a Protection Group While the Application Is Online

To add an existing application resource group to a new protection group without taking the application offline, complete the following steps on the cluster where the application resource group is online.

• Create the protection group from a cluster node.

  For more information, see How to Create and Configure an EMC Symmetrix Remote Data Facility Protection Group.

• Add the data replication device group to the protection group.

  For more information, see How to Add a Data Replication Device Group to an EMC Symmetrix Remote Data Facility Protection Group.

• Start the protection group locally.

  For more information, see How to Activate an EMC Symmetrix Remote Data Facility Protection Group.

• Add the application resource group to the protection group.

  For more information, see How to Add an Application Resource Group to an EMC Symmetrix Remote Data Facility Protection Group.

Complete the following steps on the other cluster.

• Retrieve the protection group configuration.

  For more information, see How to Replicate the EMC Symmetrix Remote Data Facility Protection Group Configuration to a Partner Cluster.

• Activate the protection group locally.

  For more information, see How to Activate an EMC Symmetrix Remote Data Facility Protection Group.

Example 2–1 Creating an EMC Symmetrix Remote Data Facility Protection Group While the Application Remains Online

This example creates a protection group without taking the application offline.

In this example, the apprg1 resource group is online on the cluster-paris cluster.

1. Create the protection group on cluster-paris.

   phys-paris-1# geopg create -d srdf -p Nodelist=phys-paris-1,phys-paris-2 \ -o Primary -s paris-newyork-ps srdfpg Protection group "srdfpg" has been successfully created

2. Add the device group, devgroup1, to the protection group.

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

3. Activate the protection group locally.

   phys-paris-1# geopg start -e local srdfpg Processing operation.... this may take a while... Protection group "srdfpg" successfully started.

4. Add an application resource group that is already online to the protection group.

   phys-paris-1# geopg add-resource-group apprg1 srdfpg Following resource groups were successfully inserted: "apprg1"

5. Verify that the application resource group was added successfully.

   phys-paris-1# geoadm status Cluster: cluster-paris Partnership "paris-newyork-ps" : OK Partner clusters : newyork Synchronization : OK ICRM Connection : OK Heartbeat "hb_cluster-paris~cluster-newyork" monitoring \ "paris-newyork-ps" OK Plug-in "ping-plugin" : Inactive Plug-in "tcp_udp_plugin" : OK Protection group "srdfpg" : Degraded Partnership : paris-newyork-ps Synchronization : OK Cluster cluster-paris : Degraded Role : Primary Configuration : OK Data replication : Degraded Resource groups : OK Cluster cluster-newyork : Unknown Role : Unknown Configuration : Unknown Data Replication : Unknown Resource Groups : Unknown

6. On one node of the partner cluster, retrieve the protection group.

   phys-newyork-1# geopg get -s paris-newyork-ps srdfpg Protection group "srdfpg" has been successfully created.

7. Activate the protection group locally on the partner cluster.

   phys-newyork-1# geopg start -e local srdfpg Processing operation.... this may take a while... Protection group "srdfpg" successfully started.

8. Verify that the protection group was successfully created and activated.

   Running the geoadm status command on cluster-paris produces the following output:

   phys-paris-1# geoadm status Cluster: cluster-paris Partnership "paris-newyork-ps" : OK Partner clusters : newyork Synchronization : OK ICRM Connection : OK Heartbeat "hb_cluster-paris~cluster-newyork" monitoring \ "paris-newyork-ps": OK Plug-in "ping-plugin" : Inactive Plug-in "tcp_udp_plugin" : OK Protection group "srdfpg" : Degraded Partnership : paris-newyork-ps Synchronization : OK Cluster cluster-paris : Degraded Role : Primary Configuration : OK Data replication : Degraded Resource groups : OK Cluster cluster-newyork : Degraded Role : Secondary Configuration : OK Data Replication : Degraded Resource Groups : OK