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. The clusters have the following roles:
If the original primary cluster, cluster-paris, has been down, confirm that the cluster is booted and that the Geographic Edition infrastructure is enabled on the cluster. For more information about booting a cluster, see Booting a Cluster in Oracle Solaris Cluster Geographic Edition System Administration Guide .
The protection group on cluster-newyork has the primary role.
The protection group on cluster-paris has either the primary role or secondary role, depending on whether cluster-paris can be reached during the takeover from cluster-newyork.
This task is necessary to finish recovery if the cluster had experienced a complete site failure.
phys-paris-1# symrdf -g device-group query
phys-paris-1# symrdf -g device-group failover
cluster-paris 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 Oracle Solaris Cluster Geographic Edition System Administration Guide .
phys-paris-1# geoadm status
phys-paris-1# geopg stop -e local protection-group
phys-paris-1# geoadm status
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
Specifies the name of the protection group
For more information about synchronizing protection groups, see Resynchronizing a Protection Group in Oracle Solaris Cluster Geographic Edition System Administration Guide .
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 Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .
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 local protection-group
Specifies the scope of the command.
By specifying a local scope, the command operates on the local cluster only.
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 Oracle Solaris Cluster Geographic Edition System Administration Guide .
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 SRDF device groups on cluster-newyork have a Synchronized RDF pair state.
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 Oracle Solaris Cluster Geographic Edition System Administration Guide .
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 data replication for each SRDF protection group.
# clresourcegroup status -v protection-group
Refer to the Status and Status Message fields that are presented for the data replication device group you want to check. For more information about these fields, see Figure 3, Table 3, Conditions That Determine the Aggregate Device Group State.
For more information about the runtime status of data replication, see Checking the Runtime Status of SRDF Data Replication.