HP StorageWorks XP Remote Web Console Software - Manual (Page 171)

Table 49 Analyzing the Currency of TrueCopy for Mainframe Sync R-VOLs
Currency of R-VOL Fence Level Status of R-VOL
Inconsistent. This R-VOL does not belong
to a TrueCopy for Mainframe pair. Data
Status
Simplex
Even if you established a TrueCopy for
Mainframe pair for this volume, you
must regard this volume as inconsistent.)
Never
Inconsistent. This R-VOL is not
synchronized because not all tracks Data
Status
Pending Duplex
have been copied from the M-VOL yet.
Never
This R-VOL must be initialized (or
copied from the M-VOL at a later time).
Current. This R-VOL is synchronized
with its M-VOL. Data Status Duplex
Needs to be analyzed. This R-VOL
requires further analysis to determine
its level of currency. Never
Inconsistent. This R-VOL is not
synchronized because not all tracks Data
Status
Suspended - initial copy failed
have been copied from the M-VOL yet.
Never
This R-VOL must be initialized (or
copied from the M-VOL at a later time).
Suspect. This R-VOL is not synchronized
with its M-VOL if any write I/Os were Data
Status
Suspended - R-VOL by operator
issued to the M-VOL after the pair was
Never
suspended. This pair should be
restarted using the Entire Volume initial
copy option, but the None option can
be used if you are sure no data on the
M-VOL changed.
Current. This R-VOL is synchronized
with its M-VOL. Data Suspended - all other types
Suspect. This R-VOL is not synchronized
with its M-VOL if any write I/Os were Status
Never
issued to the M-VOL after the pair was
suspended. Restore the consistency of
this R-VOL and update it, if required.
The system time stamp information
transferred through ERC or the time of
suspension indicated on the Detailed
Information dialog box will help to
determine the last time this R-VOL was
updated.
Analyzing the Consistency of TrueCopy for Mainframe Async R-VOLs
“Analyzing the Consistency of TrueCopy for Mainframe Async R-VOLs” (page 172) shows how to
determine the consistency of a TrueCopy for Mainframe Asynchronous R-VOL based on its pair
status and consistency status. For TrueCopy for Mainframe Asynchronous R-VOLs with a consistency
status of Volume, the volume is not consistent with other volumes in the same group, and further
analysis will be required to determine the currency of each of these R-VOLs. The currency of these
R-VOLs can be determined by using the sense information transferred via the ERC or by comparing
the contents of the R-VOL with other files which are confirmed to be current (for example, DB2 log
files). These R-VOLs should be recovered using the files which are confirmed to be current.
Using TrueCopy for Mainframe for Disaster Recovery 171