Update How to Perform a Failback-Switchover on a System That Uses Oracle ZFS Storage Appliance Replication Procedure (36175231)

The following updated procedure replaces How to Perform a Failback-Switchover on a System That Uses Oracle ZFS Storage Appliance Replication in Oracle Solaris Cluster Remote Replication Guide for Oracle ZFS Storage Appliance.

This procedure refers to the following cluster names and ZFS storage appliance names:

Original Primary Cluster: cluster-paris and the associated appliance name is paris.
Current Primary Cluster: cluster-newyork and the associated appliance name is newyork.

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.

Note:

The failback procedures apply only to clusters in a partnership. You need to perform the following procedure only once per partnership.

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.

Synchronize the replication from the newyork appliance to the paris appliance.

You must perform this task to complete a recovery when the cluster experiences a complete site failure or a takeover. Note that the data stores at cluster-newyork will have changed and must be replicated on cluster-paris before it can return to service.

Perform these steps for each replicated project in the protection group.
1. Access the Oracle ZFS Storage Appliance browser user interface (BUI) on the cluster-newyork site.
2. Select the project that you want to replicate from the Shares > Projects menu.
3. Select Replication for the project and the click Update or Sync Now.
  If Update Now or Sync Now do not appear as options, click Enable Action to start the replication. Ensure that the replication mode is set to continuous. If neither syncing a replication nor enabling a replication succeed, perform the following steps to execute a manual replication to synchronize the two sites:
  - Remove the replication action
  - Re-create the replication action
  - Enable the replication action in continuous mode
Ensure that the protection group is stopped at the cluster-paris site.
1. Determine whether the protection group on the original primary cluster, cluster-paris, is active.
```
phys-paris-1# geoadm status
```
2. Stop the protection group on the original primary cluster if active.
```
phys-paris-1# geopg stop -e local protection-group
```
  protection-group specifies the name of the protection group.
3. Verify that the protection group is stopped.
```
phys-paris-1# geoadm status
```
Remove any obsolete projects from the appliance at the cluster-paris site.

First, access the BUI on the cluster-paris site. Then, from the Shares > Projects menu, manually delete any projects that are listed in the protection group.
Resynchronize the original primary cluster, cluster-paris, with the current primary cluster, cluster-newyork.

The cluster-paris cluster forfeits its own configuration and replicates the cluster-newyork configuration locally. Then, resynchronize both the partnership configuration and the protection group configuration.
1. On cluster-paris, resynchronize the partnership.
```
phys-paris-1# geops update partnership
```
  partnership specifies the name of the partnership.
  
  Note:
  Perform this step only one time per partnership, even if you are performing a failback-switchover for multiple protection groups in the partnership.
  
  For more information about synchronizing partnerships, see Resynchronizing a Partnership in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
2. On cluster-paris, resynchronize each protection group.
  Because the local role of the protection group on cluster-newyork is now primary, this step 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.
On cluster-paris, validate the cluster configuration for each protection group.
Ensure that the protection group is not in an error state or the protection group cannot be started.
```
phys-paris-1# geopg validate protection-group
```
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.
On cluster-paris, activate each protection group.
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
```
The -e option specifies the scope of the command, where local relates to the local cluster and where global relates to both clusters. protection-group specifies the name of the protection group.

Note:
Do not use the -n option when performing a failback-switchover. You must synchronize from the current primary, cluster-newyork, to the current secondary, cluster-paris.

Because the protection group fills a secondary role, 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.
Confirm that the data is completely synchronized.

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, view the Protection Group section in the geoadm status command output.
On both partner clusters, ensure that the protection group is activated.
```
# geoadm status
```
On either cluster, perform a switchover from cluster-newyork to cluster-paris for each protection group.
```
# 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.
Ensure that the switchover is successful.
Verify that the protection group is now primary on cluster-paris and is secondary on cluster-newyork. Also verify that the state of 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 in the Status field and Status Message field for the remote replication component.
```
# clresourcegroup status -v protection-group
```