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 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.
If you use a role with Geo Management rights, ensure that the /var/cluster/geo access control lists (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 ACL applied for compatibility between the Geo Management rights profile and the data replication software.
For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
Perform this procedure from a node in the secondary cluster.
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 in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
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 C, Post-Takeover Conditions, in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
To fail back a protection group to the original cluster, see Recovering a Protection Group to a Cluster.