Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator |
1. Replicating Data With Hitachi TrueCopy and Universal Replicator Software
2. Administering Hitachi TrueCopy and Universal Replicator Protection Groups
3. Migrating Services That Use Hitachi TrueCopy and Universal Replicator Data Replication
Detecting Primary Cluster Failure
Detecting Secondary Cluster Failure
Forcing a Takeover on a System That Uses Hitachi TrueCopy or Universal Replicator Data Replication
Validations That Occur Before a Takeover
Results of a Takeover From a Replication Perspective
How to Resynchronize and Revalidate the Protection Group Configuration
Recovering From Switchover Failure
Recovering From a Hitachi TrueCopy or Universal Replicator Data Replication Error
How to Detect Data Replication Errors
How to Recover From a Hitachi TrueCopy or Universal Replicator Data Replication Error
A. Geographic Edition Properties for Hitachi TrueCopy and Universal Replicator
Perform a switchover of a Hitachi TrueCopy or Universal Replicator protection group when you want to migrate services to the partner cluster in an orderly fashion. A switchover consists of the following:
Application services are offline on the former primary cluster, cluster-paris.
For a reminder of which cluster is cluster-paris, see Example Geographic Edition Cluster Configuration in Oracle Solaris Cluster Geographic Edition System Administration Guide.
The data replication role is reversed and now continues to run from the new primary, cluster-newyork, to the former primary, cluster-paris.
Application services are brought online on the new primary cluster, cluster-newyork.
This section provides the following information:
When a switchover is initiated by using the geopg switchover command, the data replication subsystem runs several validations on both clusters. The switchover is performed only if the validation step succeeds on both clusters.
First, the replication subsystem checks that the Hitachi TrueCopy or Universal Replicator device group is in a valid aggregate device group state. Then, it checks that the local device group states on the target primary cluster, cluster-newyork, are 23, 33, 43, or 53. The local device group state is returned by the pairvolchk -g device-group-name -ss command. These values correspond to a PVOL_PAIR or SVOL_PAIR state. The Hitachi TrueCopy or Universal Replicator commands that are run on the new primary cluster, cluster-newyork, are described in the following table.
Table 3-1 Hitachi TrueCopy and Universal Replicator Switchover Validations on the New Primary Cluster
|
After a successful switchover, at the data replication level the roles of the primary and secondary volumes have been switched. The PVOL_PAIR volumes that were in place before the switchover become the SVOL_PAIR volumes. The SVOL_PAIR volumes in place before the switchover become the PVOL_PAIR volumes. Data replication will continue from the new PVOL_PAIR volumes to the new SVOL_PAIR volumes.
The Local-role property of the protection group is also switched regardless of whether the application could be brought online on the new primary cluster as part of the switchover operation. On the cluster on which the protection group had a Local role of Secondary, the Local-role property of the protection group becomes Primary. On the cluster on which the protection group had a Local-role of Primary, the Local-role property of the protection group becomes Secondary.
Before You Begin
For a successful switchover, data replication must be active between the primary and the secondary clusters and data volumes on the two clusters must be synchronized.
Before you switch over a protection group from the primary cluster to the secondary cluster, ensure that the following conditions are met:
The Geographic Edition software is running on the both clusters.
The secondary cluster is a member of a partnership.
Both cluster partners can be reached.
The protection group is in the OK state.
Caution - If you have configured the Cluster_dgs property, only applications that belong to the protection group can write to the device groups specified in the Cluster_dgs property. |
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.
The application resource groups that are a part of the protection group are stopped and started during the switchover.
# geopg switchover [-f] -m newprimarycluster protectiongroupname
Forces the command to perform the operation without asking you for confirmation
Specifies the name of the cluster that is to be the new primary cluster for the protection group
Specifies the name of the protection group
Example 3-1 Forcing a Switchover From Primary to Secondary
This example performs a switchover to the secondary cluster.
# geopg switchover -f -m cluster-newyork tcpg