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

If you are migrating data between storage systems using P/DAS, both storage systems must be
the same type (XP24000/XP20000 Disk Array).
If you need to migrate data from other vendors' storage systems onto the XP24000/XP20000 Disk
Array, contact your HP service representative.
To use TrueCopy for Mainframe Synchronous to migrate data from one volume to another:
1. Vary the R-VOL(s) offline from all attached hosts. The R-VOLs are the target volumes onto which
you are migrating the data. The M-VOLs (source volumes) can remain online.
2. Connect to the storage system containing the volume(s) to be migrated, and open the TrueCopy
for Mainframe Pair Operation window. If not already done, install the remote copy connections
and configure the ports (initiator ports for fibre) (if migrating between storage systems), and
then add the RCUs.
3. Select the correct CU, select the desired volume(s), and then start the TrueCopy for Mainframe
Synchronous pair(s) using the Add Pair dialog box.
4. Monitor the progress of the initial copy operation(s) and the status of the pair(s) on the Pair
Operation window. Refresh the window as needed. When the status has changed from
pending duplex to duplex, the M-VOL and R-VOL are identical and synchronized.
5. Use the IBM P/DAS host software function to redirect all application I/Os to the R-VOL(s)
nondisruptively. If the host system does not support P/DAS, use the following procedure to
stop using the M-VOL(s) and switch to the R-VOL(s):
a.
Quiesce all applications using the M-VOL(s).
b. When all update activity to the M-VOL(s) has stopped, connect to the MCU, select the
correct CU, and release the TrueCopy for Mainframe pair(s).
c. If the M-VOL(s) and R-VOL(s) are attached to the same host, vary the M-VOL(s) offline first,
and then vary the R-VOL(s) online. The M-VOL(s) and R-VOL(s) have the same VOLSERs
and cannot be online to the same host(s) at the same time.
d. If an R-VOL contains more cylinders than its M-VOL, update the R-VOL volume table of
contents (VTOC) using ICKDSF/REFORMAT.
e. To keep the volumes synchronized, establish the same TrueCopy for Mainframe pair(s)
in the reverse direction using the No Copy initial copy option. If the original M-VOL(s)
will be temporarily unavailable for update copy operations, you can suspend the new
pair(s) so that the new MCU keeps track of changes.
f. Start the applications with the R-VOL(s). When the original M-VOL(s) become available,
you can resynchronize the pair(s) using the Resume Pair dialog box.
The data migration and TrueCopy for Mainframe Synchronous function may decrease the
performance and increase the utilization rates.
If you specify Only M VOL for the CFW Data option, CFW data will not be migrated. Note that
there is a possibility that I/O will terminate abnormally if you access the corresponding data set
when you use R-VOL after migrating data.
Using TrueCopy for Mainframe for Duplication
TrueCopy for Mainframe enables you to make Point-in-Time (PiT) duplicates of groups of volumes.
The TrueCopy for Mainframe Asynchronous Group and Drain suspend options on Suspend Pair
dialog box can be used together to create a PiT copy, relative to an application, of an entire
TrueCopy for Mainframe Asynchronous consistency group of volumes. To produce a PiT duplicate
of an existing TrueCopy for Mainframe Asynchronous consistency group:
1. Quiesce the applications accessing the TrueCopy for Mainframe Asynchronous M-VOLs to
stop all update activity to all M-VOLs in the group.
2. After all M-VOL updates have completed, suspend the TrueCopy for Mainframe Asynchronous
group using the Group and Drain suspend options. If you are suspending the group at the
main site, you need to issue the suspend/group command to one M-VOL in the MCU. If you
178 TrueCopy for Mainframe Usage Scenarios