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

108 TrueCopy for the XP128/XP1024/XP10000/XP12000
Discontinuing TrueCopy Operations
If you plan to use TC390 for nondisruptive data migration or duplication (see ” ICKDSF Considerations for
TrueCopy Volumes ” on page 130), you will need to configure and establish TC390 operations, allow
TC390 to synchronize the volumes, redirect application I/Os (if migrating), and then discontinue TC390
operations. When you are ready to discontinue TC390 operations, you will need to perform TC390
operations in the correct order to avoid generating error messages. For example, you cannot delete an
RCU path until you have deleted all TC390 pairs still using that path and you cannot delete a group until
you have deleted all TC390A pairs in that group.
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 126). 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 101). 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 91). Check each CU image of each
MCU to verify that all RCUs have been deleted before continuing.
4. Remove the remote copy connections (physical paths). If you are not familiar with the operation of the
remote copy hardware components (for example, ESCON directors, 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 107, 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 21 on page 108).
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
RCU capacity The performance of the RCUs directly
affects the performance of the MCUs. If an
RCU becomes overloaded with heavy
update activity, MCU and system
performance can also be degraded.
Distribute TC390 remote copy operations
among several remote disk arrays to avoid
overloading any one RCU.
ESCON paths An inadequate number of ESCON paths
may decrease disk array performance.
Performing TC390 Synchronous operations
over long distances can also degrade disk
array performance. TC390A is
recommended for long distances.
Make sure to install an adequate number
of ESCON paths between the main and
remote disk arrays. This is especially
important for disk arrays that contain both
M-VOLs and R-VOLs.
Table 21 Optimizing TrueCopy operations and XP128/XP1024/XP10000/XP12000 performance
Condition Description Recommendation(s)