Use this procedure to restart an application on the original primary cluster, cluster-paris, after the data on this cluster has been resynchronized with the data on the current primary cluster, cluster-newyork.
Before You Begin
Before you perform a failback-switchover, a takeover has occurred on cluster-newyork. Ensure that the clusters have the following roles:
If the original primary cluster had been down, the cluster has been booted and that the disaster recovery framework is enabled on the cluster. For more information about booting a cluster, see Booting a Cluster in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
The protection group on the current primary cluster has the primary role.
The protection group on the original primary cluster has either the primary role or secondary role, depending on whether the original primary cluster can be reached during the takeover from the current primary cluster.
This procedure uses the example names cluster-paris for the original primary cluster and cluster-newyork for the current primary cluster.
This task is necessary to finish recovery if the cluster had experienced a complete site failure or a takeover. Data stores at cluster-newyork will have changed and will need to be replicated back to cluster-paris when it is put back in service.
Perform these steps for each project that is replicated.
This executes a manual replication to synchronize the two sites.
phys-paris-1# geoadm status
phys-paris-1# geopg stop -e local protection-group
Specifies the name of the protection group
phys-paris-1# geoadm status
The cluster-paris cluster forfeits its own configuration and replicates the cluster-newyork configuration locally. Resynchronize both the partnership and protection group configurations.
phys-paris-1# geops update partnership
Specifies the name of the partnership
For more information about synchronizing partnerships, see Resynchronizing a Partnership in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
Because the local role of the protection group on cluster-newyork is now primary, this steps ensures that the role of the protection group on cluster-paris becomes secondary.
phys-paris-1# geopg update protection-group
For more information about synchronizing protection groups, see Resynchronizing a Protection Group in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
Ensure that the protection group is not in an error state. A protection group cannot be started when it is in a error state.
phys-paris-1# geopg validate protection-group
Specifies a unique name that identifies a single protection group
For more information, see Validating a Protection Group in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
Because the protection group on cluster-paris has a role of secondary, the geopg start command does not restart the application on cluster-paris.
phys-paris-1# geopg start -e global protection-group
Specifies the scope of the command. By specifying a global scope, the command operates on both clusters.
Specifies the name of the protection group.
Because the protection group has a role of secondary, the data is synchronized from the current primary, cluster-newyork, to the current secondary, cluster-paris.
For more information about the geopg start command, see How to Activate a Protection Group in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
The data is completely synchronized when the state of the protection group on cluster-newyork is OK. The protection group has a local state of OK when the appliance data store on cluster-newyork is being updated to the cluster-paris cluster.
To confirm that the state of the protection group on cluster-newyork is OK, use the following command:
phys-newyork-1# geoadm status
Refer to the Protection Group section of the output.
# geoadm status
# geopg switchover [-f] -m cluster-paris protection-group
For more information, see How to Switch Over Replication From the Primary Cluster to the Secondary Cluster in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
cluster-paris resumes its original role as primary cluster for the protection group.
Verify that the protection group is now primary on cluster-paris and secondary on cluster-newyork and that the state for "Data replication" and "Resource groups" is OK on both clusters.
# geoadm status
Check the runtime status of the application resource group and replication for each protection group.
# clresourcegroup status -v protection-group
Refer to the Status and Status Message fields that are presented for the remote replication component you want to check.
For more information about the runtime status of replication, see Checking the Runtime Status of Oracle ZFS Storage Appliance Remote Replication.