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

a. Clear the remote copy SIMs from the RCUs before OS IPL. Connect to each RCU, open
the TrueCopy for Mainframe System Option window, and click Clear SIM.
b. Perform IPL of the remote host system.
c. Wait until the IPL is complete, and then vary the R-VOLs online (if they did not come online
automatically).
6. At this point, you may start critical applications at the remote site with the previous R-VOLs
taking the place of their M-VOLs.
Analyzing the Currency of TrueCopy for Mainframe Sync R-VOLs
“Analyzing the Currency of TrueCopy for Mainframe Sync R-VOLs” (page 173) shows how to
determine the currency of a TrueCopy for Mainframe Synchronous R-VOL based on its pair status
and M-VOL fence level setting. For TrueCopy for Mainframe Synchronous pairs with an M-VOL
fence level setting of Never, further analysis will be required to determine the currency 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.
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.
Even if you established a TrueCopy for
Mainframe pair for this volume, you
must regard this volume as inconsistent.)
Data
Status
Never
Simplex
Inconsistent. This R-VOL is not
synchronized because not all tracks
have been copied from the M-VOL yet.
This R-VOL must be initialized (or
copied from the M-VOL at a later time). Data
Status
Never
Pending Duplex
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
have been copied from the M-VOL yet.
This R-VOL must be initialized (or
copied from the M-VOL at a later time). Data
Status
Never
Suspended - initial copy failed
Suspect. This R-VOL is not synchronized
with its M-VOL if any write I/Os were
issued to the M-VOL after the pair was
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. Data
Status
Never
Suspended - R-VOL by operator
Using TrueCopy for Mainframe for Disaster Recovery 173