This section describes how to perform a protection group takeover in order to migrate services to a partner cluster. You perform a takeover when applications need to be brought online on the existing secondary partner cluster regardless of whether the data is completely synchronized between the primary and secondary ZFS datasets. The applications will be started on the existing secondary partner as a result of the takeover if the protection group has been activated on that partner.
Use the standard protection group takeover procedure to perform takeover of a ZFS snapshot replication protection group to migrate services to the existing secondary partner. For more information, see Forcing a Takeover of a Protection Group in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
Before You Begin
Ensure that the following conditions are met before you attempt a takeover:
Geographic Edition infrastructure is up and running on the secondary cluster.
Protection group is configured on the secondary cluster, and its Configuration status is OK
This procedure uses the example names paris for the current primary cluster and newyork for the current secondary cluster. The goal is to takeover the protection group to make newyork the new primary.
# geopg takeover [-f] protection-group
# geopg status protection-group
#geoadm status protection-group
Data replication is deactivated on a takeover.
# clresourcegroup status -v replication-status-rg-for-pg # clresource status -v replication-status-rs
Otherwise, activate the protection group on newyork to bring the application online. Type the following commands to check the status of the application:
# clresourcegroup status application-rg-in-pg # clresource status -g application-rg-in-pg