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

3. At the remote site, suspend all TrueCopy for Mainframe pairs at the MCUs (original RCUs) to
de-stage any pending data from cache. Confirm that the pairs are suspended before
proceeding. If an error occurs, resolve it before proceeding.
4. At the remote site, release all TrueCopy for Mainframe pairs at the MCUs (original RCUs)
using the Deleting Mode-All option for TrueCopy for Mainframe sync pairs and the Delete
Range-Group option for TrueCopy for Mainframe Asynchronous pairs. For TrueCopy for
Mainframe Asynchronous pairs, the MCU and RCU complete all pending updates before
changing the pair status to simplex.
5. At the remote site, change the TrueCopy for Mainframe settings at the MCUs (original RCUs)
to prepare for normal TrueCopy for Mainframe operations. Delete the TrueCopy for Mainframe
Asynchronous groups and the RCUs (original MCUs). If you plan to use the same remote copy
connections, reconfigure the ports (change initiator ports back to ordinary target ports for
fibre). If system option mode 114 is enabled on all MCUs and RCUs, the ports will reconfigure
automatically if you use the TSO CESTPATH command to add the pairs at the main site.
For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same
time as the SCSI path definition function of LUN Manager. The Fibre Channel interface ports
need to be configured as initiator ports or RCU target ports before the CESTPATH and
CDELPATH commands are issued.
6. If you plan to use the same channel extenders, change the operating mode back to the original
direction. The boxes/nodes connected to the MCUs must be set to channel-mode, and the
boxes/nodes connected to the RCUs must be set to device-mode.
7. At the main site, configure the initiator ports, add the RCUs, and add the TrueCopy for
Mainframe Asynchronous groups. If system option mode 114 is enabled on all MCUs and
RCUs, the ports will reconfigure automatically if you use the TSO CESTPATH command to add
the pairs at the main site.
CAUTION: Before issuing the CESTPATH command, you must make sure that the relevant
paths are offline from the host(s) (for example, configure the Chipid offline, deactivate the
LPAR, or block the port in the ESCD). If any active logical paths still exist, the add path
operation will fail because the port mode cannot be changed.
8. At the main site, establish all TrueCopy for Mainframe Asynchronous groups and TrueCopy
for Mainframe pairs in the original direction. You may use the No Copy initial copy option
because all M-VOLs and R-VOLs are synchronized. If there is any possibility that the volumes
are not 100% synchronized, use the Entire Volume initial copy option to be safe.
9. Vary the MCU and M-VOLs online, and start the applications at the main site.
Using TrueCopy for Mainframe for Data Migration
When you need to migrate data for any of the following reasons, TrueCopy for Mainframe
Synchronous can be used.
•
To load data onto new or scratch volumes (for example, new or upgraded storage system)
•
To temporarily move data off a volume to accommodate other activities (for example, repair)
•
To relocate volumes to balance workloads and distribute I/O activity evenly within and across
storage systems for the purpose of improving storage system and system performance
TrueCopy for Mainframe operations within one HP disk array can only be performed if the
ShadowImage for Mainframe option is not active on the storage system.
The TrueCopy for Mainframe initial copy operation copies the entire contents of the M-VOL to the
R-VOL. The data migration is complete when the initial copy operation completes and the pair
status changes from pending duplex to duplex. The P/DAS host software function is used with
TrueCopy for Mainframe Synchronous to complete the data migration nondisruptively.
174 TrueCopy for Mainframe Usage Scenarios