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

Table 50 Analyzing the Consistency of TrueCopy for Mainframe Async R-VOLs
Description Usable for Recovery? Status of R-VOL
These states do not usually occur during
TrueCopy for Mainframe Asynchronous
disaster recovery, because the RCU
suspends all TrueCopy for Mainframe
Asynchronous pairs when
communication with the MCU is lost.
TrueCopy for Mainframe Asynchronous
R-VOLs in these states should not be
used for disaster recovery.
Simplex volumes cannot be
distinguished from R-VOLs which have
already been released by the Delete
Pair operation.
No
No
No
Duplex
Pending Duplex
Simplex
The update sequence consistency across
these R-VOLs is ensured at the point in
time indicated by the group consistency
time. These R-VOLs can be used for
disaster recovery at the secondary
system.
Updates which were performed at the
primary system after the indicated
consistency time were probably lost.
Yes Suspended-Group
The contents of this R-VOL may be
behind the other R-VOLs in the
consistency group. If this volume must
be consistent with the other volumes in
the same group, this R-VOL should not
be used for disaster recovery.
The cause for this status is:
•
The TrueCopy for Mainframe
Asynchronous Error Level pair option
for this pair is Volume (not Group)
• This pair was suspended before the
disaster/failure, at the beginning of
the rolling disaster, or during the
initial copy operation.
No Suspended-Volume
Transferring Operations Back to the Main Site
Once the applications are running at the remote site, the next activity is to restore the main site
and transfer operations back to the main site. To transfer operations to the main site:
1. Bring up the host system at the main (primary) site, and ensure that all TrueCopy for Mainframe
components are fully operational.
2. At the main site, release all TrueCopy for Mainframe pairs at the MCUs. Use the Deleting
Mode-All option to release all TrueCopy for Mainframe sync pairs in each CU. Use the Delete
Range-Group option to release all TrueCopy for Mainframe Asynchronous pairs in each group.
Make sure to connect with all MCUs and all CUs to release all TrueCopy for Mainframe pairs.
3. At the main site, delete all TrueCopy for Mainframe Asynchronous consistency groups at the
MCUs.
4. At the main site, delete the RCUs. Remember to connect with each MCU and each CU to make
sure that all RCUs have been deleted.
5. At the main site, configure the MCU ports as needed. If you plan to use the same remote copy
connections to copy back, change the existing initiator ports to RCU target ports. If system
option mode 114 is enabled on all MCUs and RCUs, the ports will reconfigure automatically
Using TrueCopy for Mainframe for Disaster Recovery 175