JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

Introduction to Protection Groups

Creating a Protection Group That Does Not Require Data Replication

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

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins


Creating a Protection Group That Does Not Require Data Replication

Some protection groups do not require data replication. If you are using the Geographic Edition software to manage only resource groups, 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 not to use data replication.

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

How to Create a Protection Group That Is Configured Not to 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 Geographic Edition namespace. You cannot use the same protection group name in more than one partnership on the same system.

  1. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

    For more information about RBAC, see Geographic Edition Software and RBAC.

    Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

    # chmod A+user:username:rwx:allow /var/cluster/geo

    The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.

  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 partnershipname -o localrole \
    [-p property [-p…]] \
    -s partnershipname

    Specifies the name of the partnership.

    -o localrole

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

    -p propertysetting

    Specifies the properties of the protection group.

    You can specify the following properties:

    • Description – Describes the protection group.

    • External_Dependency_Allowed – Specifies whether to allow any dependencies between resource groups and resources that belong to this protection group and resource groups and resources that do not belong to this protection group.

    • 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 path to an executable command. This script is invoked during a switchover or takeover on the new primary cluster when the protection group is started on the new primary cluster. The script is invoked on the new primary cluster after the data replication role changes from secondary to primary and before the application resource groups are brought online. If the data replication role change does not succeed, then the script is not called.

      This path should be valid on all nodes of all partner clusters that can host the protection group.

    • Timeout – Specifies the timeout period for the protection group in seconds. You can change the timeout period from the default value depending on the complexity of your data replication configuration. For more information on setting the timeout period, see Table A-4.

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


    Specifies the name of the protection group.

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

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

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

This example creates a protection group that is configured to not use data replication.

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

Next Steps

See one of the following guides for information about adding resource groups to a protection group.