How to Resynchronize and Revalidate the Protection Group Configuration

Use this procedure to resynchronize and revalidate data on the original primary cluster, cluster-paris, with the data on the current primary cluster, cluster-newyork.

Before You Begin

Before you resynchronize and revalidate the protection group configuration, a takeover has occurred on cluster-newyork. The clusters now have the following roles:

• If the original primary cluster, cluster-paris, has been down, confirm that the cluster is booted and that the Sun Cluster Geographic Edition infrastructure is enabled on the cluster. For more information about booting a cluster, see Booting a Cluster in Sun 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 could be reached during the takeover from cluster-newyork.

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, resynchronize the partnership.

      # geops update partnershipname

      partnershipname

      Specifies the name of the partnership

      ---

      Note –

      You need to perform this step only once, even if you are resynchronizing multiple protection groups.

      ---

      For more information about synchronizing partnerships, see Resynchronizing a Partnership in Sun Cluster Geographic Edition System Administration Guide.

   2. 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 protectiongroupname

      protectiongroupname

      Specifies the name of the protection group

      For more information about synchronizing protection groups, see Resynchronizing a Hitachi TrueCopy Protection Group.

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

   # geopg validate protectiongroupname

   protectiongroupname

   Specifies a unique name that identifies a single protection group

   For more information, see How to Validate a Hitachi TrueCopy Protection Group.

3. 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.

   # geopg start -e local protectiongroupname

   -e local

   Specifies the scope of the command.

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

   protectiongroupname

   Specifies the name of the protection group.

   ---

   Caution –

   Do not use the -n option 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 Hitachi TrueCopy Protection Group.

4. Confirm that the data is completely synchronized.

   The state of the protection group on cluster-newyork must be OK.

   phys-newyork-1# geoadm status

   Refer to the Protection Group section of the output.

   The protection group has a local state of OK when the Hitachi TrueCopy device groups on cluster-newyork have a state of PVOL_PAIR and the Hitachi TrueCopy device groups on cluster-paris have a state of SVOL_PAIR.