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

120 Hitachi TrueCopy z/OS for HP XP12000/XP10000 and SVS 200 storage systems
To discontinue all TC390 operations:
1. Delete all TC390 pairs from the MCU(s) (Delete Pair, see ” Deleting TrueCopy volume pairs (Delete
Pair) ” on page 136). For TC390A pairs, you can use the Delete Range-Group option to delete all pairs
in a group using just one operation. Verify that the pair status has changed to Simplex for all TC390
volumes before continuing.
2. Delete the TC390A group(s) from the MCU(s) (see ” Deleting consistency groups (Delete CT Group) ” on
page 107). The RCU will automatically delete a group when all pairs in the group have been deleted.
3. Delete the RCUs (see ” Deleting an RCU (Delete RCU) ” on page 97). Check each CU image of each
MCU to verify that all RCUs have been deleted before continuing.
NOTE: If SVP system option mode 114 is enabled, you can use the CDELPATH TSO command to delete the
RCUs and automatically reset the ports.
4. Remove the remote copy connections (physical paths). If you are not familiar with the operation of the
remote copy hardware components (for example, repeaters, and switches), call HP technical support
for assistance.
5. For serial interface, reset the RCP(s) to LCP(s) at the MCU(s). For Fibre Channel interface, reset the
initiator port(s) to ordinary target(s) at the MCU(s).
Performing TrueCopy pair operations
Preparing for TrueCopy volume pair operations
Before starting TC390 operations, you must consider the relative importance of disk array I/O
performance and disaster recovery preparation. As described in ” Optimizing TrueCopy operations and
disk array performance ” on page 118, remote copy operations can affect the I/O performance of the
MCUs and RCUs. TC390 provides many options, such as initial copy options, pair options, group options,
and async options, that controls the impact of TC390 operations on I/O performance. These options can
be set separately for each pair, for each TC390A group, and for each MCU to provide maximum flexibility.
You can select options that minimize the impact of TC390 operations on disk array performance, or
options that maximize the effectiveness of TC390 operations to ensure the best level of backup data
integrity. System-level factors (for example, number of paths) can also affect TC390 operations and disk
array performance (see Table 24 on page 119).
For TC390 disaster recovery operations, you should verify that the RCUs are attached to a host server to
enable reporting of sense information and transfer of host failover information. If the remote site is
unattended, attach the RCUs to a host server at the main site so that the system administrator can monitor
the operational condition of the RCUs.
To prepare for TC390 volume pair operations, you need to identify the volumes by LDEV ID for which you
want to establish TC390 remote copy operations. You should identify volumes that are required for system
operation as well as volumes that contain important data to be backed up (for example, DB log files).
Copying these volumes to the remote site will enable faster disaster recovery than maintaining a current
version of these files at the remote site. For large databases that span multiple volumes, you should plan to
establish a TC390A consistency group for each database so that the update sequence consistency of the
database can be ensured at the remote site.
You can start creating the TC390 volume pairs as soon as you have:
• Identified the volumes that will become the TC390 M-VOLs (and R-VOLs)
• Ensured that all system and TC390 requirements have been met (see ” System requirements ” on
page 44 and ” Requirements and restrictions ” on page 46)
• Completed hardware and software installation (see ” Installing the TrueCopy hardware ” on page 49
and ” Installing the TrueCopy software ” on page 53)
• Configured the MCUs and RCUs for TC390 operations (see page 53)