HP P9000 RAID Manager Reference Guide (T1610-96037, October 2011)

is specified for a group, the data consistency of each volume in the group is checked, and all
inconsistent volumes are found in the execution log file and displayed. Paircurchk is also executed
as part of the Continuous Access Synchronous takeover (horctakeover) command.
Table 16 Data consistency displayed by the paircurchk command
CurrencyObject volume
S-VOL_takeoverPaircurchkFenceStatusAttribute
-To be confirmed
1
--SMPL
-To be confirmed
1
--P-VOL
Inconsistent
3
Inconsistent
3
DataCOPYS-VOL
Status
Never
Inconsistent
3
Inconsistent
3
Async
2
OK
4
OK
4
DataPAIR
OK
4
OK
4
Status
To be analyzedTo be analyzedNever
OK
4
To be analyzedAsync
2
PAIR
OK
4
To be analyzedPFUL
SuspectedSuspectedDataPSUS
SuspectedSuspectedStatus
SuspectedSuspectedNever
SuspectedSuspectedAsync
2
PSUS
OK
4
SuspectedPFUS
OK
4
OK
4
DataPSUE
SuspectedSuspectedStatusPDUB
SuspectedSuspectedNever
OK
4
SuspectedAsync
2
-SuspectedDataSSWS
SuspectedStatus
SuspectedNever
SuspectedAsync
2
1. To be confirmed = It is necessary to check the object volume because it is not the secondary volume.
2. Async = This applies only to asynchronous remote replication.
3. Inconsistent = Data in the volume is inconsistent because it was being copied.
4. OK = Mirroring consistency is not assured, but as S-VOL of Continuous Access Asynchronous/Cnt Ac-J, the sequence
of write data is ensured.
Syntax
paircurchk { -h | -q | -z | -I[H][M][instance#] or I[CA][BC][instance#]
| -g <group> | -d <pair Vol> | -d[g] <raw_device> [MU#]
| -d[g] <seq#> <LDEV#> [MU#] | -nomsg }
paircurchk 57