Perform this procedure to take over an individual protection group by the secondary cluster.
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 Geographic Edition software 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.
For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .
# 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 the data replication software.
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.
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 Geographic Edition Cluster Configuration.
phys-newyork-1# geopg takeover -f example-pg
For information about the state of the primary and secondary clusters after a takeover, see Appendix D, Takeover Postconditions.
To fail back a protection group to the original cluster, see Recovering a Protection Group to a Cluster.