test

Sun Cluster Geographic Edition System Administration Guide

Chapter 7 Administering Sun StorEdge Availability Suite 3.2.1 Protection Groups

This chapter describes the procedures for administering data replication with Sun StorEdge Availability Suite 3.2.1 software. The following topics are covered:

Strategies for Creating Sun StorEdge Availability Suite 3.2.1 Protection Groups

Before you begin creating protection groups, consider which of the following strategies is best for you:

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

Creating a Protection Group While the Application Is Offline

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

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.

Complete the following steps on the other cluster.

Example 7–1 Creating a Sun StorEdge Availability Suite 3.2.1 Protection Group While the Application Remains Online

This example describes how to create 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.

    First, on a node of the cluster where an application resource group is already running, check and fix any Nodelist inconsistencies that may exist between the resource group and the device group with which the resource group has affinities. Then, create the protection group with a matching Nodelist. 


    phys-paris-1# scrgadm -pvv -g apprg1 | grep Nodelist

(apprg1) Res Group Nodelist:   phys-paris-1 phys-paris-2
phys-paris-1# scconf -pvv | grep "avsdg.*group node list"
(avsdg) Device group node list: phys-paris-2, phys-paris-1

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


    phys-paris-1# scconf -c -D name=avsdg,nodelist=phys-paris-1:phys-paris-2

    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 StorEdge Availability Suite 3.2.1 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 light weight resource groups have been created and brought online. Also, verify that the Sun StorEdge Availability Suite 3.2.1 volume set has been enabled, because the Enable-volume-set property has been set 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# scstat -g

-- Resource Groups and Resources --  
       Group Name              Resources 				      
       ----------              --------- 
Resources: geo-clusterstate     - 
Resources: geo-infrastructure  geo-clustername geo-hbmonitor geo-failovercontrol 
Resources: avsdg-stor-rg       lh-paris-1 avsdg-stor
Resources: avspg-rep-rg        avsdg-rep-rs 
Resources: apprg1              avs-lh avs-stor avs-server-res avs-listener-res  


-- Resource Groups -- 

            Group Name             Node Name      State
            ----------             ---------      ----- 
Group: geo-clusterstate          phys-paris-1     Online
Group: geo-clusterstate          phys-paris-2     Online 
 
Group: geo-infrastructure        phys-paris-1     Online 
Group: geo-infrastructure        phys-paris-2     Offline
 
Group: avsdg-stor-rg             phys-paris-1     Online
Group: avsdg-stor-rg             phys-paris-2     Offline 

Group: avspg-rep-rg              phys-paris-1     Online
Group: avspg-rep-rg              phys-paris-2     Offline 

Group: apprg1                    phys-paris-1     Online
Group: apprg1                    phys-paris-2     Offline

-- Resources--  

Resource Name		            Node Name      State    Status Message 
-------------                 ---------      ------   --------------- 
Resource: geo-clustername     phys-paris-1  Online    Online - \
LogicalHostname online 
Resource: geo-clustername     phys-paris-2  Offline   Offline - \
LogicalHostname offline  
Resource: geo-hbmonitor       phys-paris-1  Online    Online - \
Daemon OK 
Resource: geo-hbmonitor       phys-paris-2  Offline   Offline

Resource: geo-failovercontrol phys-paris-1  Online    Online 
Resource: geo-failovercontrol phys-paris-2  Offline   Offline
  
Resource: lh-paris-1          phys-paris-1  Online    Online - \
LogicalHostname online 
Resource: lh-paris-1          phys-paris-2  Offline   Offline 
 
Resource: avsdg-stor          phys-paris-1  Online    Online 
Resource: avsdg-stor          phys-paris-2  Offline   Offline

Resource: avsdg-rep-rs        phys-paris-1  Online    Degraded - \
Logging 
Resource: avsdg-rep-rs        phys-paris-2  Offline   Offline 
 
Resource: avs-lh              phys-paris-1  Online    Online - \
LogicalHostname online
Resource: avs-lh              phys-paris-2  Offline   Offline

Resource: avs-server-res      phys-paris-1  Online    Online 
Resource: avs-server-res      phys-paris-2  Offline   Offline

Resource: avs-listener-res    phys-paris-1  Online    Online 
Resource: avs-listener-res    phys-paris-2  Offline   Offline

  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

      Heartbeat "hb_cluster-paris~cluster-newyork" monitoring \
"paris-newyork-ps" OK 
         Plug-in "ping-plugin"            : Inactive
         Plug-in "icrm_plugin"            : OK
         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 as follows:


    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 light weight resource groups have been created and brought online as follows:


    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# scstat -g

-- Resource Groups and Resources --

    Group Name                  Resources
    ----------                  --------- 
Resources: geo-clusterstate         -
Resources: geo-infrastructure  geo-clustername geo-hbmonitor \
geo-failovercontrol
Resources: avsdg-stor-rg       lh-newyork-1 avsdg-stor
Resources: avspg-rep-rg        avsdg-rep-rs
Resources: apprg1              avs-lh avs-stor avs-server-res avs-listener-res 

-- Resource Groups --

     Group Name                  Node Name        State
     ----------                  ---------        -----
Group: geo-clusterstate	         phys-newyork-1   Online
Group: geo-clusterstate          phys-newyork-2   Online

Group: geo-infrastructure        phys-newyork-1   Online
Group: geo-infrastructure        phys-newyork-2   Offline

Group: avsdg-stor-rg             phys-newyork-1   Online
Group: avsdg-stor-rg             phys-newyork-2   Offline

Group: avspg-rep-rg              phys-newyork-1   Online
Group: avspg-rep-rg              phys-newyork-2   Offline

Group: apprg1                    phys-newyork-1   Unmanaged
Group: apprg1                    phys-newyork-2   Unmanaged

-- Resources --

Resource Name                 Node Name       State     Status Message
-------------                 ---------       ------    ---------------
Resource: geo-clustername     phys-newyork-1  Online    Online - \
LogicalHostname online
Resource: geo-clustername     phys-newyork-2  Offline   Offline - \
LogicalHostname offline

Resource: geo-hbmonitor       phys-newyork-1  Online    Online - Daemon OK
Resource: geo-hbmonitor       phys-newyork-2  Offline   Offline

Resource: geo-failovercontrol phys-newyork-1  Online    Online
Resource: geo-failovercontrol phys-newyork-2  Offline   Offline

Resource: lh-newyork-1        phys-newyork-1  Online    Online - \
LogicalHostname online
Resource: lh-newyork-1        phys-newyork-2  Offline   Offline

Resource: avsdg-stor          phys-newyork-1  Offline   Offline
Resource: avsdg-stor          phys-newyork-2  Offline   Offline

Resource: avsdg-rep-rs        phys-newyork-1  Online    Degraded - Logging
Resource: avsdg-rep-rs        phys-newyork-2  Offline   Offline

Resource: avs-lh              phys-newyork-1  Offline   Offline
Resource: avs-lh              phys-newyork-2  Offline   Offline

Resource: avs-server-res      phys-newyork-1  Offline   Offline
Resource: avs-server-res      phys-newyork-2  Offline   Offline

Resource: avs-listener-res    phys-newyork-1  Offline   Offline
Resource: avs-listener-res    phys-newyork-2  Offline   Offline

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

    Running the geoadm status command on cluster-parisproduces the following output:


    phys-paris-1# geoadm status

Cluster: cluster-paris

Partnership "paris-newyork-ps": OK
  Partner clusters    : cluster-newyork
  Synchronization     : OK

  Heartbeat "paris-to-newyork" monitoring "cluster-newyork": OK
     Heartbeat plug-in "ping_plugin"   : Inactive
     Heartbeat plug-in "icrm_plugin"   : OK
     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

Creating, Modifying, Validating, and Deleting a Sun StorEdge Availability Suite 3.2.1 Protection Group

This section contains procedures for the following tasks:

Note –

You can create protection groups that are not configured to use data replication. To create a protection group that does not use a data replication subsystem, omit the -d data-replication-type option when you use the geopg command. The geoadm status command shows a state for data replication of NONE.

ProcedureHow to Create and Configure a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

Before you create a protection group, ensure that the following conditions are met:

Note –

Protection group names are unique in the global Sun Cluster Geographic Edition namespace. You cannot use the same protection group name in two partnerships on the same system.

You can also replicate the existing configuration of a protection group from a remote cluster to the local cluster. For more information, see Replicating the Sun StorEdge Availability Suite 3.2.1 Protection Group Configuration to a Partner Cluster

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Create a new protection group by using the geopg create command.

    This command creates a protection group on all nodes of the local cluster.


    # geopg create -s partnership-name -d avs \
-o local-role [-p property-settings [-p...]] \
protection-group-name
    -s partnership-name

    Specifies the name of the partnership

    -d avs

    Specifies that the protection group data is replicated by Sun StorEdge Availability Suite 3.2.1

    -o local-role

    Specifies the role of this protection group on the local cluster as either primary or secondary

    -p property-setting

    Sets the properties of the protection group

    The properties you can set are the following:

    • Description – describes the protection group

    • Timeout – specifies the timeout period for the protection group in seconds

    • Enable_volume_set – when set to true, specifies that the volume set will be automatically enabled at protection group creation time

      For more information about automatically enabling a volume set, see Enabling a Sun StorEdge Availability Suite 3.2.1 Volume Set.

    • Nodelist – Lists the host names of the machines that can be primary for the device group in the protection group.

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    protection-group-name

    Specifies the name of the protection group

    For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

    For more information about the geopg command, refer to the geopg(1M) man page.

    Before creating the protection group, the data replication layer validates that the configuration is correct.

    If the validation is successful, the local Configuration status is set to OK and the Synchronization status is set to Error.

    If the validation is unsuccessful, the protection group is not created.

Example 7–2 Creating and Configuring a Protection Group

The following example illustrates how to create a Sun StorEdge Availability Suite 3.2.1 protection group on cluster-paris, which is set as the primary cluster:


phys-paris-1# geopg create -s paris-newyork-ps -d avs -o primary \
-p Nodelist=phys-paris-1,phys-paris-2 avspg

ProcedureHow to Modify a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

Before modifying the configuration of your protection group, ensure that the protection group you want to modify exists locally.

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Modify the configuration of the protection group.

    This command modifies the properties of a protection group on the local cluster. If the partner cluster contains a protection group of the same name, this command also propagates the new configuration information to the partner cluster.


    # geopg set-prop -p property-settings[-p...] protection-group-name
    -p property-setting

    Sets the properties of the protection group

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    protection-group-name

    Specifies the name of the protection group

    For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

    For more information about the geopg command, refer to the geopg(1M) man page.

Example 7–3 Modifying the Configuration of a Protection Group

The following example illustrates how to modify the timeout property of the protection group that was created in Example 7–2:


# geopg set-prop -p Timeout=300 avspg
How the Data Replication Subsystem Validates the Modified Protection Group

When you launch the geopg set-prop command, the data replication subsystem revalidates the protection group with the new configuration information. If the validation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.

If the Configuration status is OK on the local cluster, but the validation is in unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.

ProcedureHow to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

When the Configuration status of a protection group is displayed as Error in the geoadm status output, you can validate the configuration by using the geopg validate command. This command checks the current state of the protection group and its entities.

If the protection group and its entities are valid, then the Configuration status of the protection groups is set to OK. If the geopg validate command finds error in the configuration files, then the command displays a message about the error and the configuration remains in the error state. In such a case, you can fix the error in the configuration, and issue thegeopg validate command again.

This command validates the configuration of the protection group on the local cluster only. To validate the protection group configuration on the partner cluster, issue the command again on the partner cluster.

Before validating the configuration of a protection group, ensure that the protection group you want to validate exists locally and that the common agent container is online on all nodes of both clusters in the partnership.

Steps

  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 Sun Cluster Geographic Edition Software and RBAC.

  2. Validate the configuration of the protection group.

    This command validates the configuration of the protection group on the local cluster only. 


    # geopg validate protection-group-name
    protection-group-name

    Specifies a unique name that identifies a single protection group.

Example 7–4 Validating the Configuration of a Protection Group

The following example illustrates how to validate a protection group:


# geopg validate avspg

How the Data Replication Layer Validates the Application Resource Groups and Data Replication Entities

During protection group validation, the Sun StorEdge Availability Suite 3.2.1 data replication layer validates the application resource groups and the data replication entities as follows:

If the Enable_volume_set property of a successfully validated device group is set to True, then volume sets defined in the /var/cluster/geo/avs/avsdg-volset.ini file are enabled. Other volume sets for the device group are disabled. If you want to enable the other volume sets, you can add the volume sets to the /var/cluster/geo/avs/avsdg-volset.ini file or set the Enable_volume_set property to False.

When validation is complete, the Sun Cluster Geographic Edition software creates the lightweight resource group, the replication resource group, and the resources for this replication resource group, if nonexistent, and brings them online. If a resource group or resource of the same name already exists, the Sun Cluster Geographic Edition operations may modify their properties. Sun Cluster Geographic Edition software cannot create a new resource group or resource of the same name if one already exists.

The Configuration status is set to OK after successful validation. If validation is not successful, the Configuration status is set to Error.

ProcedureHow to Delete a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

To delete the protection group on every cluster, run the geopg delete command on each cluster where the protection group exists.

Before deleting a protection group, ensure that the following conditions are met.

Note –

To keep the application resource groups online while deleting a protection group, you must remove the application resource groups from the protection group.

Steps

  1. Log in to one of the nodes on the cluster where you want to delete the protection group, for example cluster-paris.

    The cluster-paris is the primary cluster. See Figure 2–1 for For a a sample cluster configuration.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Delete the protection group.

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


    # geopg delete protection-group-name
    protection-group-name

    Specifies the name of the protection group

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

Example 7–5 Deleting a Protection Group

The following example illustrates how to delete a protection group from both partner clusters. 


# rlogin cluster-paris -l root
cluster-paris# geopg delete avspg
# rlogin cluster-newyork -l root
cluster-newyork# geopg delete avspg
Example 7–6 Deleting a Protection Group While Keeping Application Resource Groups Online

The following example illustrates how to keep two application resource groups (apprg1 and apprg2) online while deleting their protection group, avspg. Remove the application resource groups from the protection group, then delete the protection group. 


# geopg remove-resource-group apprg1,apprg2 avspg 
# geopg stop -e global avspg
# geopg delete avspg

Creating a Protection Group That Does Not Require Data Replication

Some of the protection groups do not require data replication. If you are using the Sun Cluster Geographic Edition software to manage only resource groups and to handle data replication differently, you can create protection groups that do not replicate data. The geoadm status command displays that these protection groups are in the Degraded state. This section describes how to configure your protection group to not use data replication.

For information about how to create a Sun StorEdge Availability Suite 3.2.1 protection group that requires data replication, seeHow to Create and Configure a Sun StorEdge Availability Suite 3.2.1 Protection Group.

Note –

You cannot add device groups to a protection group that does not use data replication.

ProcedureHow to Create a Protection Group That Is Configured to Not Use Data Replication

Before You Begin

Before you create a protection group, ensure that the following conditions are met:

Note –

Protection group names are unique in the global Sun Cluster Geographic Edition namespace. You cannot use the same protection group name in more than one partnership on the same system.

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Create a new protection group by using the geopg create command.

    This command creates a protection group on the local cluster.


    # geopg create -s partnership-name -o local-role \
[-p property-settings [-p...]] \
protection-group-name
    -s partnership-name

    Specifies the name of the partnership

    -o local-role

    Specifies the role of this protection group on the local cluster as either Primary or Secondary

    -p property-setting

    Sets the properties of the protection group

    The properties you can set are the following:

    • Description – Describes the protection group.

    • Timeout – Specifies the timeout period for the protection group in seconds.

    • RoleChange_ActionArgs – Specifies a string that follows system-defined arguments at the end of the command line when the role-change callback command runs.

    • RoleChange_ActionCmd – Specifies the absolute path to the executable command to run when the primary cluster of the protection group changes. This path should be valid on all partner clusters that host the protection group.

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    protection-group-name

    Specifies the name of the protection group

    For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

    For more information about the geopg command, refer to the geopg(1M) man page.

Example 7–7 Creating and Configuring a Protection Group That Is Configured to Not Use Data Replication

The following example illustrates how to create an protection group that is configured to not use data replication. 


# geopg create -s paris-newyork-ps -o primary example-pg
Next Steps

See Administering Sun StorEdge Availability Suite 3.2.1 Application Resource Groups for information on adding resource groups to a protection group.

Administering Sun StorEdge Availability Suite 3.2.1 Application Resource Groups

To be highly available, an application must be managed as a resource in an application resource group.

All of the entities that you configure for the application resource group on the primary cluster, such as application data resources, configuration files, and resource groups, must be replicated to the secondary cluster. The resource group names must be identical on both clusters. Also, the data that the application resource uses must be replicated to the secondary cluster.

This section contains information about the following tasks:

ProcedureHow to Add an Application Resource Group to a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

You can add an existing resource group to the list of application resource groups for a protection group. Before you add an application resource group to a protection group, ensure that the following conditions are met:

The protection group can be activated or deactivated and the resource group can be either Online or Offline.

If the resource group is Offline and the protection group is activated after the configuration of the protection group has changed, then the protection group's local state becomes Error.

If the resource group to add is Online and the protection group is deactivated, the request is rejected. You must activate the protection group before adding an activate resource group.

Steps

  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 Sun Cluster Geographic Edition Software and RBAC.

  2. Add an application resource group to the protection group.


    # geopg add-resource-group resource-group-list protection-group
    resource-group-list

    Specifies the name of the application resource group

    You can specify more than one resource group in a comma-separated list.

    protection-group

    Specifies the name of the protection group

    This command adds an application resource group to a protection group on the local cluster. Then the command propagates the new configuration information to the partner cluster if the partner cluster contains a protection group of the same name.

    For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

    If the add operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.

    If the Configuration status is OK on the local cluster, but the add operation is unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.

    After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. Then the application resource group is affected by protection group operations such as start, stop, switchover, and takeover.

    If the application resource group is a failover type resource group that shares affinities with one of the device groups in the same protection group, the Sun Cluster Geographic Edition software alters its RG_affinities property to include a strong, positive affinity to an internal resource group, called a lightweight resource group. This affinity includes failover delegation.

    The application resource group must not have strong, positive affinities that have failover delegation with other resource groups. Otherwise, trying to include a strong positive affinity with failover delegation on the lightweight resource group fails.

    The Sun Cluster Geographic Edition software also creates strong dependencies between the HAStoragePlus resource in the application resource group and the HAStoragePlus resource in the lightweight resource group for this device group. This redirection occurs when the protection group is brought online or when an online application resource group is added to an online protection group.

    Do not modify dependencies and resource group affinities between application resource groups and light weight resource groups.

Example 7–8 Adding an Application Resource Group to a Sun StorEdge Availability Suite 3.2.1 Protection Group

The following example illustrates how to add two application resource groups, apprg1 and apprg2, to avspg:


# geopg add-resource-group apprg1,apprg2 \
avspg

ProcedureHow to Delete an Application Resource Group From a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

You can remove an existing application resource group from a protection group without altering the application resource group's state or contents.

Before you remove an application resource group from a protection group, ensure that the following conditions are met:

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Remove the application resource group from the protection group.

    This command removes an application resource group from a protection group on the local cluster. If the partner cluster contains a protection group of the same name, the application resource group is also removed from the partner cluster's protection group.


    # geopg remove-resource-group resource-group-list \
 protection-group
    resource-group-list

    Specifies the name of the application resource group

    You can specify more than one resource group in a comma-separated list.

    protection-group

    Specifies the name of the protection group

    If the resource group being removed shares dependencies with other resource groups in the protection group, then you must remove all the resource groups that share dependencies in the same command.

    If the remove operation failed on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.

    If the Configuration status is OK on the local cluster, but the remove operation is unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.

    Sun Cluster Geographic Edition software removes the affinity and resource dependencies between the application resource group and the lightweight resource group.

Example 7–9 Deleting an Application Resource Group From a Protection Group

The following example illustrates how to remove two application resource groups, apprg1 and apprg2, from avspg:


# geopg remove-resource-group apprg1,apprg2 \
avspg

Administering Sun StorEdge Availability Suite 3.2.1 Data Replication Device Groups

This section describes the following tasks for administering data replication device groups in a Sun StorEdge Availability Suite 3.2.1 protection group:

For details about configuring a Sun StorEdge Availability Suite 3.2.1 protection group, see How to Create and Configure a Sun StorEdge Availability Suite 3.2.1 Protection Group.

ProcedureHow to Add a Data Replication Device Group to a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

A protection group is the container for the application resource groups, which contain data for services that are protected from disaster. Sun Cluster Geographic Edition software protects the data by replicating it from the primary cluster to the secondary cluster. By adding a Sun Cluster device group to a protection group, Sun Cluster Geographic Edition software monitors the replication status of all volumes in the device group that belong to a Sun StorEdge Availability Suite 3.2.1 volume set. Sun Cluster Geographic Edition software also controls the role and state of the volume set during protection group operations like start, stop, switchover, and takeover.

Before you add a device group to a protection group, ensure that the following conditions are met:

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Add a data replication device group to the protection group.

    This command adds a device group to a protection group on the local cluster and propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.


    # geopg add-device-group -p property-settings [-p...] \
AVS-device-group-name protection-group-name
    -p property-settings

    Sets the properties of the data replication device group

    The Sun StorEdge Availability Suite 3.2.1 specific properties you can set are the following:

    • Local_logical_host – Specifies the name of the local logical host that is used to replicate the device group

    • Remote_logical_host – Specifies the name of the remote logical host that is used to replicate the device group

    • Enable_volume_set – Specifies whether the volume sets that are given in the file will be automatically enabled. Set to either True or False

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    AVS-device-group-name

    Specifies the name of the new data replication device group

    protection-group-name

    Specifies the name of the protection group that will contain the new data replication device group

    For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

    For more information about the geopg command, refer to the geopg(1M) man page.

Example 7–10 Adding a Data Replication Device Group to a Sun StorEdge Availability Suite 3.2.1 Protection Group

The following example illustrates how to create a Sun StorEdge Availability Suite 3.2.1 data replication device group in the avspg protection group:


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

How the Data Replication Subsystem Verifies the Device Group

When the device group controlled by Sun StorEdge Availability Suite 3.2.1 is added to a protection group, the data replication layer verifies that the device group exists and that the value of its Nodelist property contains the same entries in the same order as the Nodelist property of the protection group.

When the geopg add-device-group command runs, a lightweight resource group for the device group is created and brought online. The lightweight resource group contains the following resources:

For more information about lightweight resource groups and their resources, see Sun StorEdge Availability Suite 3.2.1 Lightweight Resource Groups.

When you run the geopg add-device-group command, a replication resource of the type GeoCtlAVS is created in the replication resource group of each device group in the protection group and brought online. For information about the format of the replication resource group, see Sun StorEdge Availability Suite 3.2.1 Replication Resource Groups.

The Nodelist property of the lightweight resource group and replication resource group contains the same entries in the same order as the Nodelist property of the protection group.

If a resource or resource group of the same name is already configured on the local cluster, Sun Cluster Geographic Edition verifies the configuration and sets the Configuration to Error if the configuration is not correct.

If the Enable_volume_set property of this device group is set to True, then volume sets that are defined in the /var/cluster/geo/avs/AVS-devicegroup-volset.ini file are enabled. Otherwise, Sun Cluster Geographic Edition software controls and monitors all volume sets that you enable manually by using the Sun StorEdge Availability Suite 3.2.1 commands.

If the geopg add-device-group command is unsuccessful, the configuration of the protection group is not modified.

If the geopg add-device-group command is successful and the Configuration status on the local cluster is set to OK, then the new configuration is propagated to the partner cluster. This propagation causes the whole protection group configuration to be revalidated on the partner cluster. During revalidation, the same entities are created on the partner cluster, including the lightweight resource group and the replication resource group. Volume sets are also enabled on the partner clusters if the /var/cluster/geo/avs/AVS-devicegroup-volset.ini file exists on the partner cluster and contains correctly defined volume sets. If the validation is unsuccessful, then the Configuration status on the partner cluster is set to Error on the partner cluster.

Caution – Caution –

Do not change, remove, or bring offline these resources or resource groups. Lightweight resource groups, replication resource groups, and their resources are internal entities managed by Sun Cluster Geographic Edition software and should be administered by using only the Sun Cluster Geographic Edition commands. Altering the configuration or state of these entities directly with Sun Cluster commands could result in unrecoverable failure.

Conditionally, if the validation of the device group on the partner cluster is successful, the volume sets defined in the /var/cluster/geo/avs/AVS-devicegroup-volset.ini file are enabled on the partner cluster. The Enable_volume_set property of this device group must be set to true. Other volume sets of the device group are disabled.

After the device group has been added to the protection group, you can enable or disable the volume sets of the device group directly by using the Sun StorEdge Availability Suite 3.2.1 commands. The /var/cluster/geo/avs/AVS-devicegroup-volset.ini file is only consulted when the protection group that contains the device group is successfully validated for the first time.

ProcedureHow to Modify a Sun StorEdge Availability Suite 3.2.1 Data Replication Device Group

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Modify the device group.

    This command modifies the properties of a device group in a protection group on the local cluster. Then the command propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.


    # geopg modify-device-group -p property-settings [-p...] \
AVS-device-group-name protection-group-name
    -p property-settings

    Sets the properties of the data replication device group

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    AVS-device-group-name

    Specifies the name of the new data replication device group

    protection-group-name

    Specifies the name of the protection group that will contain the new data replication device group

ProcedureHow to Delete a Data Replication Device Group From a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

You might need to delete a data replication device group from a protection group if you added a data replication device group to a protection group. Normally, after an application is configured to write to a set of disks, you would not change the disks.

Before you remove a data replication device group, ensure that the following conditions are met:

For information about deleting protection groups, refer to How to Delete a Sun StorEdge Availability Suite 3.2.1 Protection Group.

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Remove the device group.

    This command removes a device group from a protection group on the local cluster. Then the command propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.

    This command removes the device group from the protection group. This command also disables all volume sets associated with the device group and deletes the lightweight resource group and replication resource group for this device group.


    # geopg remove-device-group AVS-device-group-name protection-group-name
    AVS-device-group-name

    Specifies the name of the data replication device group

    protection-group-name

    Specifies the name of the protection group

Example 7–11 Deleting a Replication Device Group From a Sun StorEdge Availability Suite 3.2.1 Protection Group

The following example illustrates how to delete a data replication device group from a Sun StorEdge Availability Suite 3.2.1 protection group:


# geopg remove avsdg avspg

Replicating the Sun StorEdge Availability Suite 3.2.1 Protection Group Configuration to a Partner Cluster

You can replicate the configuration of a protection group to the partner cluster either before or after you configure data replication, resource groups, and resources on both clusters.

ProcedureHow to Replicate the Sun StorEdge Availability Suite 3.2.1 Protection Group Configuration to a Partner Cluster

Before You Begin

Before you replicate the configuration of a Sun StorEdge Availability Suite 3.2.1 protection group to a partner cluster, ensure that the following conditions are met:

Steps

  1. Log in to phys-newyork-1.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Replicate the protection group configuration to the partner cluster by using the geopg get command.

    This command retrieves the configuration information of the protection group from the remote cluster and creates the protection group on the local cluster.


    # geopg get -s partnership-name \
AVS-protection-group
    -s partnership-name

    Specifies the name of the partnership from which the protection group configuration information should be gathered.

    AVS-protection-group

    Specifies the name of the protection group.

    Note –

    The geopg get command replicates Sun Cluster Geographic Edition related entities. For information about how to replicate Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Example 7–12 Replicating the Sun StorEdge Availability Suite 3.2.1 Protection Group to a Partner Cluster

This example illustrates how to replicate the configuration of avspg to cluster-newyork.

The configuration of the protection group is retrieved from the remote cluster, in this example cluster-paris and then validated by the data replication subsystem on the local cluster, cluster-newyork.

If the validation is successful, the Configuration status is set to OK and the protection group is created on the local cluster. This protection group contains a device group and an application group that are configured identically to the device group and application group on the remote cluster.

If the validation fails, the Configuration status is set to Error. Fix the cause of the error and revalidate the protection group or delete the invalid protection group from all nodes on the local cluster.


# rlogin phys-newyork-1 -l root
phys-newyork-1# geopg get -s paris-newyork-ps avspg

Activating and Deactivating a Protection Group

When you activate a protection group, it assumes the role that you assigned to it during configuration.

For more information about configuring protection groups, see How to Create and Configure a Sun StorEdge Availability Suite 3.2.1 Protection Group.

ProcedureHow to Activate a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

You can activate a protection group in the following ways:

When a protection group is activated on a primary or secondary cluster, the outcome depends on the type of data replication you are using. If you are using Sun StorEdge Availability Suite 3.2.1 software, data replication can only be started from the primary cluster. So, when you activate a protection group on the secondary cluster, the activation will not start data replication.

Steps

  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 Sun Cluster Geographic Edition Software and RBAC.

  2. Activate the protection group.

    This command activates the protection group on the local cluster.

    When you activate a protection group on the primary cluster, its application resource groups are also brought online.


    # geopg start -e scope [-n] AVS-protection-group
    -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 that deploy the protection group.

    Note –

    The property values, such as Global and Local, are not case sensitive.

    -n

    Prevents the start of data replication at protection group startup

    If you omit this option, the data replication subsystem starts at the same time as the protection group and the command performs the following operations on each device group in the protection group:

    • Verifies that the role configured for the replication resource is the same as the role of the protection group on the local cluster.

    • Verifies that the role of the volume sets associated with the device group is the same as the role of the protection group on the local cluster.

    • If the role of the protection group on the local cluster is secondary, unmounts the local volumes defined in all volume sets associated with the device group.

    • If the role of the protection group on the local cluster is primary, enables the autosynchronization feature of the Sun StorEdge Availability Suite 3.2.1 remote mirror software. Also, resynchronizes the volume sets associated with the device group.

    AVS-protection-group

    Specifies the name of the protection group

    The geopg start command uses the scswitch -Z -g resource-groups command to bring resource groups and resources online. For more information about using this command, see the scswitch(1M) man page.

    The geopg start command performs the following actions if the role of the protection group is primary on the local cluster:

    • The command executes a script defined in the RoleChange_ActionCmd.

    • The command brings the application resource groups in the protection group online on the local cluster.

    • If the application resource group is a failover type resource group that shares affinities with one of the device groups in the same protection group, the command adds strong, positive affinities and failover delegation between the application resource group and the lightweight resource group.

      The application resource group must not have strong, positive affinities with failover delegation. Otherwise, the attempt to add strong, positive affinities with failover delegation with the lightweight resource group will fail.

    • The command creates strong dependencies between the HAStoragePlus resource in the application resource group and the HAStoragePlus resource in the lightweight resource group for this device group.

    If the command fails, the Configuration status might be set to Error, depending on the cause of the failure. The protection group remains deactivated, but data replication may be started and some resource groups may be brought online. You should run geoadm status to get the status of your system.

    If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group.

Example 7–13 Activating a Sun StorEdge Availability Suite 3.2.1 Protection Group Globally

The following example illustrates how to activate a protection group globally:


# geopg start -e global avspg
Example 7–14 Activating a Sun StorEdge Availability Suite 3.2.1 Protection Group Locally

The following example illustrates how to activate a protection group on a local cluster only. This local cluster might be a primary cluster or a secondary cluster, depending on the cluster's role.


# geopg start -e local avspg

ProcedureHow to Deactivate a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

You can deactivate a protection group in the following ways:

The result of deactivating a protection group on primary or secondary cluster depends on the type of data replication you are using. If you are using Sun StorEdge Availability Suite 3.2.1 software, data replication can only be stopped from the primary cluster. So, when you deactivate a protection group on the secondary cluster, this deactivate command will not stop data replication.

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Deactivate the protection group.

    This command deactivates the protection group on all nodes of the local cluster.

    When you deactivate a protection group, its application resource groups are also taken offline.


    # geopg stop -e scope [-D] protection-group-name
    -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 while leaving the protection group online

    If you omit this option, the data 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 the following actions:

    • Removal of resource group affinities and resource dependencies between the application resource groups in the protection group and the internal resource group

    • Taking the application resource groups offline and putting them in an unmanaged state

    protection-group-name

    Specifies the name of the protection group

    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.

    If the geopg stop command fails, execute the geoadm status command to see the status of each component. For example, the Configuration status might be set to Error depending upon the cause of the failure. The protection group might remain activated even though some resource groups might be taken offline. The protection group might be deactivated with data replication running.

    If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group.

Example 7–15 Deactivating a Sun StorEdge Availability Suite 3.2.1 Protection Group on All Clusters

The following example illustrates how to deactivate a protection group on all clusters:


# geopg stop -e global avspg
Example 7–16 Deactivating a Sun StorEdge Availability Suite 3.2.1 Protection Group on a Local Cluster

The following example illustrates how to deactivate a protection group on the local cluster:


# geopg stop -e local avspg
Example 7–17 Stopping Sun StorEdge Availability Suite 3.2.1 Data Replication While Leaving the Protection Group Online

The following example illustrates how to stop only data replication on a local cluster:


# geopg stop -e local -D avspg

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


# geopg stop -e local avspg
Example 7–18 Deactivating a Sun StorEdge Availability Suite 3.2.1 Protection Group While Keeping Application Resource Groups Online

The following example illustrates how to keep two application resource groups, apprg1 and apprg2, online while deactivating their protection group, avspg.

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


    # geopg remove-resource-group apprg1,apprg2 avspg

  2. Deactivate the protection group.


    # geopg stop -e global avspg

Resynchronizing a Sun StorEdge Availability Suite 3.2.1 Protection Group

You can resynchronize the configuration information of the local protection group with the configuration information retrieved from the partner cluster. You need to resynchronize a protection group when its Synchronization status in the output of the geoadm status command is Error.

For example, you might need to resynchronize protection groups after booting the cluster. For more information, see Booting a Cluster.

Resynchronizing a protection group updates only entities that are related to Sun Cluster Geographic Edition. For information about how to update Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Resynchronize a Sun StorEdge Availability Suite 3.2.1 Protection Group

Before You Begin

The protection group must be deactivated on the cluster where you run the geopg update command.

Steps

  1. Log in to one of the cluster nodes.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Resynchronize the protection group.


    # geopg update protection-group-name
    protection-group-name

    Specifies the name of the protection group

Example 7–19 Resynchronizing a Sun StorEdge Availability Suite 3.2.1 Protection Group

The following example illustrates how to resynchronize a protection group:


# geopg update avspg

Checking the Runtime Status of Sun StorEdge Availability Suite 3.2.1 Data Replication

You can obtain an overall view of the status of replication, as well as a more detailed runtime status of the Sun StorEdge Availability Suite 3.2.1 software from the status of the replication resource groups. The following sections describe the procedures for checking each status.

Printing a Sun StorEdge Availability Suite 3.2.1 Runtime Status Overview

The status of each Sun StorEdge Availability Suite data replication resource indicates the status of replication on a particular device group. The status of all the resources under a protection group are aggregated in the replication status.

To view the overall status of replication, look at the protection group state as described in the following procedure.

ProcedureHow to Check the Overall Runtime Status of Replication

Steps

  1. Access a node of a cluster where the protection group is defined.

    You must be assigned the Basic Solaris User RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

  2. Check the runtime status of replication.


    # geoadm status

    Refer to the Protection Group section of the output for replication information. The information that is printed by this command includes the following:

    • Whether the local cluster is enabled for partnership participation

    • Whether the local cluster is involved in a partnership

    • Status of the heartbeat configuration

    • Status of the defined protection groups

    • Status of current transactions

  3. Check the runtime status of data replication for each Sun StorEdge Availability Suite 3.2.1 protection group.


    # scstat -g

    Refer to the Status and Status Message fields that are presented for the data replication device group you want to check. For more information about these fields, see Table 7–1.

Printing a Detailed Sun StorEdge Availability Suite 3.2.1 Runtime Status

You must create one replication resource group for each protection group. The name of the replication resource group has the following format:


avs-protection-group-name-rep-rg

If you add a Sun StorEdge Availability Suite 3.2.1 device group to a protection group, the Sun Cluster Geographic Edition software creates a resource for each device group. This resource monitors the status of replication for its device group. The name of each resource has the following format:


avs-devicegroup-name-rep-rs

You can monitor the state of the replication resource group to give you the overall status of replication. Use the scstat -g command to obtain the State and Status Message values for the replication resource group. The State is Online while the resource is online.

The following table describes the Status and State Message values that are returned by the scstat command when the State of the Sun StorEdge Availability Suite 3.2.1 replication resource group is Online.

Table 7–1 State and Status Messages of an Online Sun StorEdge Availability Suite 3.2.1 Replication Resource Group

Status 

Status Message 

Faulted 

Replication service disabled 

Faulted 

Incorrect role 

Faulted 

Volume failed 

Faulted 

Bitmap failed 

Faulted 

Queue failed 

Faulted 

Need sync 

Faulted 

Need reverse sync 

Faulted 

Reverse synching 

Degraded 

Synching 

Degraded 

Queuing 

Degraded 

Logging 

Online 

Replicating 

For more details about these values, refer to the Sun StorEdge Availability Suite 3.2.1 Remote Mirror Software Administration and Operations Guide.

For more information about the scstat command, see the scstat(1M) man page.