Hitachi G200 - Checking S-VOL Consistency with the P-VOL

2. Analyze the consistency of the S-VOLs, based on pair status and P-VOL
fence level setting. See Checking S-VOL consistency with the P-VOL on
page 9-4.
3. Perform file recovery as needed.
4. Run the CCI horctakeover or pairsplit-RS on the S-VOL.
5. Complete file recovery procedures.
6. Vary the S-VOLs online.
7. At the secondary site, start critical host operations, with the previous S-
VOLs now the P-VOLs.
Checking S-VOL consistency with the P-VOL
An S-VOL's consistency refers to whether S-VOL data is identical to data in
the P-VOL. This is dependent on your Fence Level setting, which determines
whether data is copied to the P-VOL if an error occurs during an update to the
S-VOL.
The following table shows S-VOL consistency information, based on Device
Manager - Storage Navigator pair status and the P-VOL fence level setting.
S-VOL status Type Fence level Consistency of S-VOL
Unpaired -- Data, Status,
Never
Not consistent. The S-VOL does not belong to a pair.
Even if you have created a pair using this volume, if the
pair status is still unpaired, you must regard its data as
not consistent with the P-VOL.
COPY -- Data, Status,
Never
Not consistent. The S-VOL is not synchronized because
not all tracks have been copied from the P-VOL yet. This
S-VOL must be initialized (or copied from the P-VOL at a
later time).
PAIR -- Data, Status Consistent. The S-VOL is synchronized with its P-VOL.
Never Needs to be analyzed*. The S-VOL requires further
analysis to determine its level of consistency.
PSUE Initial copy
failed
Data, Status,
Never
Not consistent. The S-VOL is not synchronized because
not all tracks have been copied from the P-VOL yet. The
S-VOL must be initialized (or copied from the P-VOL at a
later time).
PSUS S-VOL by
operator
Data, Status,
Never
Suspect. The S-VOL is not synchronized with its P-VOL if
any write I/Os were issued to the P-VOL after the pair
was split. The pair should be released and restarted
using Entire Volume for the Initial Copy Type option. If
you are sure that no data on the P-VOL changed, you
can use None for Initial Copy Type.
PSUS or PSUE All other
types
Data Consistent. The S-VOL is synchronized with its P-VOL.
Status,
Never
Suspect. The S-VOL is not synchronized with its P-VOL if
any write I/Os were issued to the P-VOL after the pair
was split. Restore the consistency of the S-VOL and
update it, if required. The time of suspension indicated
on the Last Update Time field of the Detailed Information
9-4
Disaster recovery
Hitachi TrueCopy® User Guide for Hitachi Virtual Storage Platform Gx00 and Fx00 Models