Sun Cluster Geographic Edition System Administration Guide

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.