Go to main content

Administering the Disaster Recovery Framework for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: June 2019

How to Force Immediate Takeover of a Protection Group by a Secondary Cluster

Perform this procedure to take over an individual protection group by the secondary cluster.

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface, if you do not need to use the –f force option. Click Partnerships, click the partnership name to go to its page, highlight the protection group name, and click Takeover. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Administering an Oracle Solaris Cluster 4.4 Configuration.

Note -  To take over a set of protection groups that are configured as a multigroup, instead follow procedures in How to Take Over a Multigroup.

Before You Begin

Before you force the secondary cluster to assume the activity of the primary cluster, ensure that the following conditions are met:

  • The disaster recovery framework is up and running on the secondary cluster.

  • The secondary cluster is a member of a partnership.

  • The Configuration status of the protection group is OK on the secondary cluster.

  • If you are using EMC Symmetrix Remote Data Facility, ensure that no LUNs in the data replication device group are in the SyncInProg state. Otherwise, the application might fail to start on the new primary cluster due to data inconsistencies.

Perform this procedure from a node in the secondary cluster.

  1. Assume the root role or assume a role that is assigned the Geo Management rights profile.

    For more information, see Disaster Recovery Framework Rights Profiles in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

    Note -  If you use a role with Geo Management rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, assume the root role 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 rights profile and the data replication software.

  2. Initiate the takeover.
    phys-newyork-1# geopg takeover [-f] protection-group-name

    Forces the command to perform the operation without your confirmation, even if the primary cluster for a protection group in the multigroup is reachable and the protection group is active on that cluster.


    Specifies the name of the protection group.

Example 33  Forcing a Takeover by a Secondary Cluster

The following example forces the takeover of the protection group example-pg by the secondary cluster cluster-newyork.

The node phys-newyork-1 is the first node of the secondary cluster. For a reminder of which node is phys-newyork-1, see Example Disaster Recovery Framework Cluster Configuration in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

phys-newyork-1# geopg takeover -f example-pg

Next Steps

For information about the state of the primary and secondary clusters after a takeover, see Appendix D, Takeover Postconditions, in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

To fail back a protection group to the original cluster, see Recovering a Protection Group to a Cluster.