For validation purposes, Sun Cluster Geographic Edition gives each Hitachi TrueCopy device group a state according to the current state of its pair. This state is returned by the pairvolchk -g devicegroup -ss command.
The remainder of this section describes the individual device group states and how these states are validated against the local role of the protection group.
An individual Hitachi TrueCopy device group can be in one of the following states:
SMPL
Regular Primary
Regular Secondary
Takeover Primary
Takeover Secondary
The state of a particular device group is determined by using the value that is returned by the pairvolchk -g devicegroup -ss command. The following table describes the device group state associated with the values returned by the pairvolchk command.
Table 2–1 Individual Hitachi TrueCopy Device Group States
Output of pairvolchk |
Individual Device Group State |
---|---|
11 = SMPL |
SMPL |
22 / 42 = PVOL_COPY 23 / 42 = PVOL_PAIR 26 / 46 = PVOL_PDUB 47 = PVOL_PFUL 48 = PVOL_PFUS |
Regular Primary |
24 / 44 = PVOL_PSUS 25 / 45 = PVOL_PSUE For these return codes, determining the individual device group category requires that the horcmd process be active on the remote cluster so that the remote-pair-state for this device group can be obtained. |
Regular Primary, if remote-cluster-state !=SSWS or Takeover Secondary, if remote-cluster-state == SSWS SSWS, when you use the pairdisplay -g devicegroup -fc command. |
32 / 52 = SVOL_COPY 33 / 53 = SVOL_PAIR 35 / 55 = SVOL_PSUE 36 / 56 = SVOL_PDUB 57 = SVOL_PFUL 58 = SVOL_PFUS |
Regular Secondary |
34 / 54 = SVOL_PSUS |
Regular Secondary, if local-cluster-state !=SSWS or Takeover Primary, if local-cluster-state == SSWS SSWS, when you use the pairdisplay -g devicegroup -fc command. |
If a protection group contains only one Hitachi TrueCopy device group, then the aggregate device group state is the same as the individual device group state.
When a protection group contains multiple Hitachi TrueCopy device groups, the aggregate device group state is obtained as described in the following table.
Table 2–2 Conditions That Determine the Aggregate Device Group State
Condition |
Aggregate Device Group State |
---|---|
All individual device group states are SMPL |
SMPL |
All individual device group states are either Regular Primary or SMPL |
Regular Primary |
All individual device group states are either Regular Secondary or SMPL |
Regular Secondary |
All individual device group states are either Takeover Primary or SMPL |
Takeover Primary |
All individual device group states are either Takeover Secondary or SMPL |
Takeover Secondary |
The aggregate device group state cannot be obtained for any other combination of individual device group states. This is considered a pair-state validation failure.
The local role of a Hitachi TrueCopy protection group is validated against the aggregate device group state as described in the following table.
Table 2–3 Validating the Aggregate Device Group State Against the Local Role of a Protection Group
Aggregate Device Group State |
Valid Local Protection Group Role |
---|---|
SMPL |
primary or secondary |
Regular Primary |
primary |
Regular Secondary |
secondary |
Takeover Primary |
primary |
Takeover Secondary |
secondary |
This example validates the state of a Hitachi TrueCopy device group against the role of the Hitachi TrueCopy protection group to which it belongs.
First, the protection group is created as follows:
phys-paris-1# geopg create -s paris-newyork-ps -o primary -d truecopy tcpg |
A device group, devgroup1, is added to the protection group, tcpg, as follows:
phys-paris-1# geopg add-device-group -p fence_level=async devgroup1 tcpg |
The current state of a Hitachi TrueCopy device group, devgroup1, is provided 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 - |
The pairvolchk -g <DG> -ss command is run and returns a value of 23.
phys-paris-1# pairvolchk -g devgroup1 -ss parivolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC] phys-paris-1# echo $? 23 |
The output of the pairvolchk command is 23, which corresponds in Table 2–1 to an individual device group state of Regular Primary. Because the protection group contains only one device group, the aggregate device group state is the same as the individual device group state. The device group state is valid because the local role of the protection group, specified by the -o option, is primary, as specified in Table 2–3.