How the State of the Hitachi TrueCopy or Universal Replicator Data Replication Component Is Validated

Language:

For validation purposes, Geographic Edition gives each Hitachi TrueCopy or Universal Replicator data replication component 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 data replication component states and how these states are validated against the local role of the protection group.

Determining the State of an Individual Hitachi TrueCopy or Universal Replicator Data Replication Component

An individual Hitachi TrueCopy or Universal Replicator data replication component can be in one of the following states:

SMPL
Regular Primary
Regular Secondary
Takeover Primary
Takeover Secondary

The state of a particular data replication component is determined by using the value that is returned by the pairvolchk -g devicegroup -ss command. The following table describes the data replication component state associated with the values returned by the pairvolchk command.

Table 7 Individual Hitachi TrueCopy and Universal Replicator Data Replication Component States

Output of `pairvolchk`	Individual Data Replication Component 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 data replication component category requires that the `horcmd` process be active on the remote cluster so that the `remote-pair-state` for this data replication component 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.

Determining the Aggregate Hitachi TrueCopy or Universal Replicator Data Replication Component State

If a protection group contains only one Hitachi TrueCopy or Universal Replicator data replication component, then the aggregate data replication component state is the same as the individual data replication component state.

When a protection group contains multiple Hitachi TrueCopy or Universal Replicator data replication components, the aggregate data replication component state is obtained as described in the following table.

Table 8 Conditions That Determine the Aggregate Data Replication Component State

Condition	Aggregate Data Replication Component State
All individual data replication component states are `SMPL`	`SMPL`
All individual data replication component states are either `Regular Primary` or `SMPL`	`Regular Primary`
All individual data replication component states are either `Regular Secondary` or `SMPL`	`Regular Secondary`
All individual data replication component states are either `Takeover Primary` or `SMPL`	`Takeover Primary`
All individual data replication component states are either `Takeover Secondary` or `SMPL`	`Takeover Secondary`

The aggregate data replication component state cannot be obtained for any other combination of individual data replication component states. This is considered a pair-state validation failure.

Validating the Local Role of the Protection Group Against the Aggregate Data Replication Component State

The local role of a Hitachi TrueCopy or Universal Replicator protection group is validated against the aggregate data replication component state as described in the following table.

Table 9 Validating the Aggregate Data Replication Component State Against the Local Role of a Protection Group

Aggregate Data Replication Component State	Valid Local Protection Group Role
`SMPL`	`primary` or `secondary`
`Regular Primary`	`primary`
`Regular Secondary`	`secondary`
`Takeover Primary`	`primary`
`Takeover Secondary`	`secondary`

Example 10 Validating the Aggregate Data Replication Component State

This example validates the state of a Hitachi TrueCopy or Universal Replicator data replication component against the role of the Hitachi TrueCopy or Universal Replicator 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 -p Ctgid=5 hdspg

A data replication component, devgroup1, is added to the protection group, hdspg, as follows:

phys-paris-1# geopg add-replication-component -p Fence_level=async devgroup1 hdspg

The current state of a Hitachi TrueCopy or Universal Replicator data replication component, 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 Figure 7, Table 7, Individual Hitachi TrueCopy and Universal Replicator Data Replication Component States to an individual data replication component state of Regular Primary. Because the protection group contains only one data replication component, the aggregate data replication component state is the same as the individual data replication component state. The data replication component state is valid because the local role of the protection group, specified by the –o option, is primary, as specified in Figure 9, Table 9, Validating the Aggregate Data Replication Component State Against the Local Role of a Protection Group.