You can deactivate a protection group on the following levels:
Globally – Deactivates a protection group on both clusters where the protection group is configured
On the primary cluster only – Secondary cluster remains active
On the secondary cluster only – Primary cluster remains active
Deactivating a Hitachi TrueCopy or Universal Replicator protection group on a cluster has the following effect on the data replication layer:
The data replication configuration of the protection group is validated. During validation, the current local role of the protection group is compared with the aggregate data replication component state as described in Figure 9, Table 9, Validating the Aggregate Data Replication Component State Against the Local Role of a Protection Group. If validation is successful, data replication is stopped.
Data replication is stopped on the data replication components that are configured for the protection group, whether the deactivation occurs on a primary or secondary cluster.
Deactivating a protection group has the following effect on the application layer:
When a protection group is deactivated on the primary cluster, all of the application resource groups that are configured for the protection group are stopped and unmanaged.
When a protection group is deactivated on the secondary cluster, the resource groups on the secondary cluster are not affected. Application resource groups that are configured for the protection group might remain active on the primary cluster, depending on the activation state of the primary cluster.
The Hitachi TrueCopy or Universal Replicator command that is used to stop data replication depends on the following factors:
Aggregate data replication component state
Local role of the protection group
Current pair state
The following table describes the Hitachi TrueCopy or Universal Replicator command used to stop data replication for each of the possible combinations of factors. In the commands, dg is the data replication component name.
You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Chapter 4, Administering RBAC in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
When you deactivate a protection group, its application resource groups are also unmanaged.
# geopg stop -e scope [-D] protection-group
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.
Specifies that only data replication should be stopped and the protection group should be online.
If you omit this option, the data replication subsystem and the protection group are both stopped.
Specifies the name of the protection group.
This example illustrates how the Geographic Edition framework determines the Hitachi TrueCopy or Universal Replicator command that is used to stop data replication.
The current state of the Hitachi TrueCopy or Universal Replicator data replication component, devgroup1, is provided in the output of the pairdisplay command:
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 data replication component, devgroup1, is added to the protection group as follows:
phys-paris-1# geopg add-replication-component -p Fence_level=async devgroup1 hdspg
The Geographic Edition framework runs 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, hdspg, is deactivated by using the geopg stop command.
phys-paris-1# geopg stop -s local hdspg
The Geographic Edition framework runs the pairsplit -g devgroup1 command at the data replication level.
If the command is successful, the state of devgroup1 is provided in the output of the pairdisplay command:
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 -Example 19 Deactivating a Protection Group on All Clusters
This example deactivates a protection group on all clusters.
# geopg stop -e global hdspgExample 20 Deactivating a Protection Group on a Local Cluster
This example deactivates a protection group on the local cluster.
# geopg stop -e local hdspgExample 21 Stopping Data Replication While Leaving the Protection Group Online
This example stops only data replication on a local cluster.
# geopg stop -e local -D hdspg
If the administrator decides later to deactivate both the protection group and its underlying data replication subsystem, the administrator can rerun the command without the –D option:
# geopg stop -e local hdspgExample 22 Deactivating a Hitachi TrueCopy or Universal Replicator Protection Group While Keeping Application Resource Groups Online
This example keeps two application resource groups, apprg1 and apprg2, online while deactivating their protection group, hdspg, on both clusters.
Remove the application resource groups from the protection group.
# geopg remove-resource-group apprg1,apprg2 hdspg
Deactivate the protection group.
# geopg stop -e global hdspg