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

138 TrueCopy for the XP128/XP1024/XP10000/XP12000
transferred through ERC or compare the contents of the R-VOL with other files that are confirmed to be
current, such as DB2 log files. These R-VOLs should be recovered using the files that are confirmed to be
current.
Transferring Operations Back to the Main Site
After 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.
NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same
time as the SCSI path definition function of LUN Management. The Fibre Channel interface ports need to
be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are
issued.
To transfer operations to the main site:
1. Bring up the host system at the main (primary) site and ensure that all TC390 components are fully
operational.
2. At the main site, delete all TC390 pairs at the MCUs. The Delete Pair by Force option must be used
because the previous R-VOLs are now in the simplex state at the remote site. Use the Delete All Pairs
option to delete all TC390 sync pairs in each CU image. Use the Delete-Group option to delete all
TC390A pairs in each group. Make sure to connect with all MCUs and all CU images to delete all
TC390 pairs.
3. At the main site, delete all TC390A consistency groups at the MCUs.
4. At the main site, delete the RCUs. Remember to connect with each MCU and each CU image to verify
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 RCPs to LCPs and change the existing initiator ports to
RCU target ports. If SVP mode 114 is enabled on all MCUs and RCUs, the ports will reconfigure
automatically if you use the CESTPATH command to add the pairs at the secondary site.
Table 24 Analyzing the consistency of TrueCopy Asynchronous R-VOLs
Status of R-VOL Usable for
Recovery?
Description
Duplex
Pending Duplex
Simplex
No
No
No
These states do not usually occur during TC390A disaster recovery
because the RCU suspends all TC390A pairs when communication with
the MCU is lost. TC390A R-VOLs in these states should not be used for
disaster recovery.
Simplex volumes cannot be distinguished from R-VOLs that have already
been deleted by the Delete Pair operation.
Suspended-Group Yes 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 that were performed at the primary system after the indicated
consistency time were probably lost.
Suspended-Volume No 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 TC390A Error Level pair option for this pair is Volume (not Group).
Also, this pair was suspended before the disaster/failure, at the
beginning of the rolling disaster, or during the initial copy operation.