You can deactivate a protection group in the following ways:
Globally, meaning you deactivate a protection group on both the primary and the secondary cluster where the protection group is configured
On the secondary cluster only, so that the primary cluster remains active
On a primary cluster, after the protection group was previously deactivated on the secondary cluster
Deactivating a Hitachi TrueCopy protection group on a cluster has the following impact on the data replication layer:
The data replication configuration of the protection group is validated. During validation, the protection group's current local role is compared with the aggregate device group state as described in Table 10–3. If validation is successful, data replication is stopped.
Data replication is stopped on the data replication device groups that are configured for the protection group, no matter whether the deactivation occurs on a primary or secondary cluster.
Deactivating a protection group has the following impact on the application layer:
When a protection group is deactivating on the primary cluster, all of the application resource groups configured for the protection group are stopped and unmanaged.
When a protection group is deactivating on the secondary cluster, the resource groups on the secondary cluster are not effected. Application resource groups configured for the protection group may remain active on the primary cluster, depending on the activation state of the primary cluster.
The Hitachi TrueCopy command used to stop data replication depends on the following factors:
Aggregate device group state
Local role of the protection group
Current pair state
The following table describes the Hitachi TrueCopy command used to stop data replication for each of the possible combinations of factors. In the commands, dg is the device group name.
Table 10–5 Commands Used to Stop Hitachi TrueCopy Data Replication
Aggregate Device Group State |
Valid Local Protection Group Role |
Hitachi TrueCopyStop Command |
---|---|---|
SMPL |
primary or secondary |
No command is issued because no data is being replicated. |
Regular Primary |
primary |
If the local state code is 22, 23, 26, 29, 42, 43, 46, or 47, then the following command is issued: pairsplit -g dg [-l] If the local state code is 11, 24, 25, 44, 45, or 48, then no command is issue because no data is being replicated. |
Regular Secondary |
secondary |
If the local state code is 32, 33, 35, 36, 39, 52, 53, 55, 56, or 57, the following command is issued: pairsplit -g dg If the local state code is 33 or 53 and the remote state is PSUE, no command is issued to stop replication. If the local state code is 11, 34, 54, or 58, then no command is issue because no data is being replicated. |
Takeover Primary |
primary |
No command is issued because no data is being replicated. |
Takeover Secondary |
secondary |
No command is issued because no data is being replicated. |
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.
Deactivate the protection group.
When you deactivate a protection group, its application resource groups are also taken offline.
# geopg stop -e scope [-D] protection-group-name |
Specifies the scope of the command
If the scope is Local, then the command operates on the local cluster only. If the scope is Global, the command operates on both clusters where the protection group is deployed.
The property values, such as Global and Local, are not case sensitive.
Specifies that only data replication should be stopped while leaving the protection group online.
If you omit this option, the data replication subsystem and the protection group are both stopped.
Specifies the name of the protection group.
The following example illustrates how the Sun Cluster Geographic Edition software determines the Hitachi TrueCopy command used to stop data replication.
The current state of the Hitachi TrueCopy device group, devgroup1, is given in the output of the pairdisplay command as follows:
phys-paris-1# pairdisplay -g devgroup1 Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M devgroup1 pair1(L) (CL1-A , 0, 1) 12345 1..P-VOL PAIR ASYNC,54321 609 - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL PAIR ASYNC,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..P-VOL PAIR ASYNC,54321 610 - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL PAIR ASYNC,----- 2 - |
A device group, devgroup1, is added to the protection group as follows:
phys-paris-1# geopg add-device-group -p fence_level=async devgroup1 tcpg |
The Sun Cluster Geographic Edition software executes the pairvolchk -g <DG> -ss command at the data replication level, which returns a value of 43.
pairvolchk -g devgroup1 -ss Volstat is P-VOL.[status = PAIR fence = ASYNC] phys-paris-1# echo $? 43 |
Next, the protection group, tcpg, is deactivated by using the geopg stop command.
phys-paris-1# geopg stop -s local tcpg |
The Sun Cluster Geographic Edition software executes the pairsplit -g devgroup1 command at the data replication level.
If the command is successful, the state of devgroup1 is given in the output of the pairdisplay command as follows:
phys-paris-1# pairdisplay -g devgroup1 Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M devgroup1 pair1(L) (CL1-A , 0, 1) 12345 1..P-VOL PSUS ASYNC,54321 609 - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL SSUS ASYNC,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..P-VOL PSUS ASYNC,54321 610 - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL SSUS ASYNC,----- 2 - |
The following example illustrates how to deactivate a protection group on all clusters:
# geopg stop -e global tcpg |
The following example illustrates how to deactivate a protection group on the local cluster:
# geopg stop -e local tcpg |
The following example illustrates how to stop only data replication on a local cluster:
# geopg stop -e local -D tcpg |
If the administrator decides later to deactivate both the protection group and its underlying data replication subsystem, the administrator can reissue the command without the -D option:
# geopg stop -e local tcpg |
The following example illustrates how to keep two application resource groups, apprg1 and apprg2, online while deactivating their protection group, tcpg on both clusters.
Remove the application resource groups from the protection group:
# geopg remove-resource-group apprg1,apprg2 tcpg |
Deactivate the protection group:
# geopg stop -e global tcpg |