How to Perform a Failback-Switchover on a System That Uses Sun StorEdge Availability Suite 3.2.1 Replication

Use this procedure to restart an application on the original primary cluster, cluster-paris, after this cluster's data 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 now have the following roles:

• 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 the protection group could be reached during the takeover.

Steps

1. Resynchronize the original primary cluster, cluster-paris, with the current primary cluster, cluster-newyork.

   cluster-paris forfeits its own configuration and replicates the cluster-newyork configuration locally. Resynchronize both the partnership and protection group configurations.

   1. On cluster-paris, deactivate the protection group on the local cluster.

      # geopg stop -e Local protection-group-name

      -e Local

      Specifies the scope of the command

      By specifying a local scope, the command operates on the local cluster only.

      protection-group-name

      Specifies the name of the protection group

      If the protection group is already deactivated, the state of the resource group in the protection group is probably Error. The state is Error because the application resource groups are managed and offline.

      Deactivating the protection group will result in the application resource groups no longer being managed, clearing the Error state.

   2. On cluster-paris, resynchronize the partnership.

      # geops update partnership-name

      partnership-name

      Specifies the name of the partnership

      ---

      Note –

      You need to perform this step only once, even if you are performing a failback-switchover for multiple protection groups.

      ---

      For more information about synchronizing partnerships, see Resynchronizing a Partnership.

   3. On cluster-paris, resynchronize each protection group.

      Because the role of the protection group on cluster-newyork is primary, this step ensures that the role of the protection group on cluster-paris is secondary.

      # geopg update protection-group-name

      protection-group-name

      Specifies the name of the protection group

      For more information about synchronizing protection groups, see Resynchronizing a Sun StorEdge Availability Suite 3.2.1 Protection Group.

2. On cluster-paris, validate the cluster's configuration for each protection group.

   # geopg validate protection-group-name

   protection-group-name

   Specifies a unique name that identifies a single protection group

   For more information, see How to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group.

3. On cluster-paris, activate each protection group.

   When you activate a protection group, its application resource groups are also brought online.

   # geopg start -e Global protection-group-name

   -e Global

   Specifies the scope of the command

   By specifying a Global scope, the command operates on both clusters where the protection group is deployed.

   protection-group-name

   Specifies the name of the protection group

   ---

   Note –

   The -n option must not be given when doing a failback-switchover because the data needs to be synchronized from the current primary, cluster-newyork, to the current secondary, cluster-paris.

   ---

   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 Sun StorEdge Availability Suite 3.2.1 Protection Group.

4. Confirm that the data is completely synchronized.

   First, confirm that the state of the protection group on cluster-newyork is OK.

   phys-newyork-1# geoadm status

   Refer to the Protection Group section of the output.

   Next, confirm that all resources in the replication resource group, AVS-protection-group-name-rep-rg, report a status of OK.

   phys-newyork-1# scstat -g

5. On either cluster, perform a switchover from cluster-newyork to cluster-paris for each protection group.

   # geopg switchover [-f] -m cluster-paris protection-group-name

   For more information, see How to Switch Over a Sun StorEdge Availability Suite 3.2.1 Protection Group From Primary to Secondary.

   cluster-paris resumes its original role as primary cluster for the protection group.

6. Ensure that the switchover was performed successfully by using the geoadm status on either cluster to verify that the replication resource and the application resource groups and resources are online.

   Also, you must verify that the protection group is now primary on cluster-paris and secondary on cluster-newyork and that “Data replication” and “Resource groups” are listed in OK states for both clusters.

   # geoadm status