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 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.
Resynchronize the original primary cluster, cluster-paris, with the current primary cluster, cluster-newyork.
The cluster cluster-paris forfeits its own configuration and replicates the cluster-newyork configuration locally. Resynchronize both the partnership and protection group configurations.
On cluster-paris, deactivate the protection group on the local cluster.
# geopg stop -e Local protectiongroupname |
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.
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 results in the application resource groups no longer being managed, clearing the Error state.
On cluster-paris, resynchronize the partnership.
# geops update partnershipname |
Specifies the name of the partnership
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.
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 |
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.
On cluster-paris, validate the configuration for each protection group.
# geopg validate protectiongroupname |
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.
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 protectiongroupname |
Specifies the scope of the command.
By specifying a Global scope, the command operates on both clusters where the protection group is deployed.
Specifies the name of the protection group.
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 Sun StorEdge Availability Suite 3.2.1 Protection Group.
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, AVSprotectiongroupname-rep-rg, report a status of OK.
phys-newyork-1# scstat -g |