Strategies for Creating Sun StorageTek Availability Suite Protection Groups

Before you begin creating protection groups, consider the following strategies:

• Stopping the application before creating the protection group

  This strategy is the most straightforward. However, because the protection group is not brought online until the end of the process, you must unmanage the application resource group to add it to the protection group.

• Creating the protection group while the application remains online

  While this strategy enables you to create a protection group without any application outage, it requires issuing more commands.

Before you create a protection group by using the steps in the following sections, ensure that the following prerequisites are met.

• The application has been configured by Sun Cluster software on both clusters.

• Corresponding device groups are configured for data replication.

Creating a Protection Group While the Application Is Offline

To create a protection group while the application resource group is offline, complete the following steps.

• Create the protection group from a node on one cluster.

  For more information, see How to Create and Configure a Sun StorageTek Availability Suite 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 a Sun StorageTek Availability Suite Protection Group.

• Take the application resource group to the unmanaged state.

• Add the application resource group to the protection group on one cluster.

  For more information, see How to Add an Application Resource Group to a Sun StorageTek Availability Suite Protection Group.

• On the other cluster, retrieve the protection group configuration.

  For more information, see How to Replicate the Sun StorageTek Availability Suite Protection Group Configuration to a Partner Cluster.

• From either cluster, activate the protection group globally.

  For more information, see How to Activate a Sun StorageTek Availability Suite Protection Group.

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 node on one cluster.

  For more information, see How to Create and Configure a Sun StorageTek Availability Suite 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 a Sun StorageTek Availability Suite Protection Group.

• Activate the protection group locally.

  For more information, see How to Activate a Sun StorageTek Availability Suite Protection Group.

• Add the application resource group to the protection group.

  For more information, see How to Add an Application Resource Group to a Sun StorageTek Availability Suite Protection Group.

Complete the following steps on the other cluster.

• Retrieve the protection group configuration.

  For more information, see How to Replicate the Sun StorageTek Availability Suite Protection Group Configuration to a Partner Cluster.

• Activate the protection group locally.

  For more information, see How to Activate a Sun StorageTek Availability Suite Protection Group.

Example 2–1 Creating a Sun StorageTek Availability Suite 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 the cluster-paris cluster.

   1. On a node of the cluster where an application resource group is already running, check and fix any Nodelist inconsistencies that might exist between the resource group and the device group with which the resource group has affinities.

   2. Create the protection group with a matching Nodelist.

      phys-paris-1# clresourcegroup show -v apprg1 | grep Nodelist Nodelist: phys-paris-1 phys-paris-2 phys-paris-1# cldevicegroup show -v avsdg1 | grep "Node List:" Node List: phys-paris-2, phys-paris-1

   The node list of the device group is in a different order from the node list of the resource group. The order of the node list of the device group is changed as follows:

   phys-paris-1# cldevicegroup set -p preferenced=true \ -n phys-paris-1,phys-paris-2 avsdg

   You can also change the node list of a resource group to meet this requirement.

   The protection group is created with a Nodelist identical to the Nodelist of the resource group and device group:

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

2. Add the Sun StorageTek Availability Suite device group, avsdg, to the protection group.

   phys-paris-1# geopg add-device-group -p Local_logical_host=lh-paris-1 \ -p Remote_logical_host=lh-newyork-1 -p Enable_volume_set=True avsdg avspg

3. Verify that the data replication resource groups and the lightweight resource groups have been created and are online. Also, verify that the Sun StorageTek Availability Suite volume set has been enabled by setting the Enable-volume-set property to True.

   phys-paris-1# dsstat name t s pct role ckps dkps tps svt /avsdg/rdsk/d100 P L 100.00 net - 0 0 0 /avsdg/rdsk/d101 bmp 0 0 0 0 phys-paris-1# clresource list -v Resource Name Resource Type Resource Group ------------- ------------- -------------- geo-clustername SUNW.LogicalHostname:2 geo-infrastructure geo-hbmonitor SUNW.HBmonitor geo-infrastructure geo-failovercontrol SUNW.scmasa geo-infrastructure lh-paris-1 SUNW.LogicalHostname:2 avsdg-stor-rg avsdg-stor SUNW.HAStoragePlus:4 avsdg-stor-rg avsdg-rep-rs SUNW.GeoCtlAVS avspg-rep-rg avs-lh SUNW.LogicalHostname:2 apprg1 avs-stor SUNW.HAStoragePlus:4 apprg1 avs-server-res SUNW.oracle_server:6 apprg1 avs-listener-res SUNW.oracle_listener:5 apprg1 phys-paris-1# clresourcegroup status === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ geo-clusterstate phys-paris-1 No Online phys-paris-2 No Online geo-infrastructure phys-paris-1 No Online phys-paris-2 No Offline avsdg-stor-rg phys-paris-1 No Online phys-paris-2 No Offline avspg-rep-rg phys-paris-1 No Online phys-paris-2 No Offline apprg1 phys-paris-1 No Online phys-paris-2 No Offline phys-paris-1# clresource status === Cluster Resources === Resource Name Node Name State Status Message ------------- --------- ----- -------------- geo-clustername phys-paris-1 Online Online - LogicalHostname online. phys-paris-2 Offline Offline geo-hbmonitor phys-paris-1 Online Online phys-paris-2 Offline Offline geo-failovercontrol phys-paris-1 Online Online phys-paris-2 Offline Offline lh-paris-1 phys-paris-1 Online Online - LogicalHostname online. phys-paris-2 Offline Offline avsdg-stor phys-paris-1 Online Online phys-paris-2 Offline Offline avsdg-rep-rs phys-paris-1 Online Degraded - Logging phys-paris-2 Offline Offline avs-lh phys-paris-1 Online Online - LogicalHostname online. phys-paris-2 Offline Offline avs-stor phys-paris-1 Online Online phys-paris-2 Offline Offline avs-server-res phys-paris-1 Online Online phys-paris-2 Offline Offline avs-listener-res phys-paris-1 Online Online phys-paris-2 Offline Offline

   For the Sun StorageTek Availability Suite 4.0 software, this command is located at /usr/sbin/dsstat. For the Sun StorEdge Availability Suite 3.2.1 software, this command is located at /usr/opt/SUNWesm/sbin/dsstat.

4. Activate the protection group locally.

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

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

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

   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 "avspg" : Unknown Partnership : paris-newyork-ps Synchronization : Error Cluster cluster-paris : Degraded Role : Primary Activation State : Activated Configuration : OK Data replication : Degraded Resource groups : OK Cluster cluster-newyork : Unknown Role : Unknown Activation State : 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 avspg Protection group "avspg" has been successfully created.

7. Verify that the data replication resource groups and the lightweight resource groups have been created and brought online.

   phys-newyork-1# dsstat name t s pct role ckps dkps tps svt /avsdg/rdsk/d100 S L 100.00 net - 0 0 0 /avsdg/rdsk/d101 bmp 0 0 0 0 phys-newyork-1# clresource list -v Resource Name Resource Type Resource Group ------------- ------------- -------------- geo-clustername SUNW.LogicalHostname:2 geo-infrastructure geo-hbmonitor SUNW.HBmonitor geo-infrastructure geo-failovercontrol SUNW.scmasa geo-infrastructure lh-newyork-1 SUNW.LogicalHostname:2 avsdg-stor-rg avsdg-stor SUNW.HAStoragePlus:4 avsdg-stor-rg avsdg-rep-rs SUNW.GeoCtlAVS avspg-rep-rg avs-lh SUNW.LogicalHostname:2 apprg1 avs-stor SUNW.HAStoragePlus:4 apprg1 avs-server-res SUNW.oracle_server:6 apprg1 avs-listener-res SUNW.oracle_listener:5 apprg1 phys-newyork-1# clresourcegroup status === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ geo-clusterstate phys-newyork-1 No Online phys-newyork-2 No Online geo-infrastructure phys-newyork-1 No Online phys-newyork-2 No Offline avsdg-stor-rg phys-newyork-1 No Online phys-newyork-2 No Offline avspg-rep-rg phys-newyork-1 No Online phys-newyork-2 No Offline apprg1 phys-newyork-1 No Unmanaged phys-newyork-2 No Unmanaged phys-newyork-1# clresource status === Cluster Resources === Resource Name Node Name State Status Message ------------- --------- ----- -------------- geo-clustername phys-newyork-1 Online Online - LogicalHostname online. phys-newyork-2 Offline Offline geo-hbmonitor phys-newyork-1 Online Online phys-newyork-2 Offline Offline geo-failovercontrol phys-newyork-1 Online Online phys-newyork-2 Offline Offline lh-newyork-1 phys-newyork-1 Online Online - LogicalHostname online. phys-newyork-2 Offline Offline avsdg-stor phys-newyork-1 Online Online phys-newyork-2 Offline Offline avsdg-rep-rs phys-newyork-1 Online Degraded - Logging phys-newyork-2 Offline Offline avs-lh phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline avs-stor phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline avs-server-res phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline avs-listener-res phys-newyork-1 Offline Offline phys-newyork-2 Offline Offline

   For the Sun StorageTek Availability Suite 4.0 software, this command is located at /usr/sbin/dsstat. For the Sun StorEdge Availability Suite 3.2.1 software, this command is located at /usr/opt/SUNWesm/sbin/dsstat.

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

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

9. 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 : cluster-newyork Synchronization : OK ICRM Connection : OK Heartbeat "paris-to-newyork" monitoring "cluster-newyork": OK Heartbeat plug-in "ping_plugin" : Inactive Heartbeat plug-in "tcp_udp_plugin": OK Protection group "tcpg" : OK Partnership : "paris-newyork-ps" Synchronization : OK Cluster cluster-paris : OK Role : Primary PG activation state : Activated Configuration : OK Data replication : OK Resource groups : OK Cluster cluster-newyork : OK Role : Secondary PG activation state : Activated Configuration : OK Data replication : OK Resource groups : OK