A Migrating Secondary Asynchronous Periodic Remote Copy Volume Groups - HP 3PAR StoreServ 7200 2-node Manual

A Migrating Secondary Asynchronous Periodic Remote Copy
Volume Groups
Peer Motion allows the seamless migration of data from a legacy system to a modern array. This
appendix describes the procedures for migrating secondary-storage Remote Copy volumes to a
new system by using Peer Motion.
When configuring peer motion, it may be necessary to make modifications to the FC switch, as
the WWNs will change when moving from peer nodes to host modes. Peer motion provides the
same LUN for the new volume as was presented by the old volume.
Migrating primary Remote Copy volume groups and secondary synchronous Remote Copy volume
groups follows the same procedures as volumes not associated with Remote Copy as described
throughout this guide.
This section provides instructions for migrating secondary periodic Remote Copy volumes with the
HP 3PAR Command Line Interface (CLI).
The HP 3PAR Management Console (MC) does not support these procedures.
For more information about Remote Copy, see the HP 3PAR Remote Copy Software User's Guide.
For more information about the HP 3PAR CLI, see the HP 3PAR Command Line Interface Reference.
Follow this procedure for each volume you are migrating.
1. On the source system, stop the periodic RC group and create a snapshot of the primary virtual
volume. When a virtual volume is dismissed with the keepsnap option, it automatically
creates a snapshot of the virtual volume. Issue the following commands:
# stoprcopygroup <rcpm_group>
# dismissrcopyvv
2. On the source system, rename the snapshot created with the keepsnap option to something
descriptive. The system-generated backup name uses the sv.#.rcpy.xxx.yyy.zzz format.
Issue the following command:
# setvv
3. On the Remote Copy secondary system, create a snapshot of the secondary volume. Issue the
following command:
# createsv <old_secondary_vv_ss> <old_secondary_vv>
4. On the secondry system, export the snapshot created in
Issue the following command:
# createvlun <old_secondary_vv_ss> <lun> <backup_system>
5. On the destination system (the new Remote Copy primary), admit the volume exported from
the secondary system in 4. Issue the following commands:
# showtarget -rescan
# showtarget -lun <node_www>
# admitvv <vv_name>:<disk_lun_www>
# importvv -tpvv -snap <old_secondary_vv_ss> -snp_cpg cpg_pri cpg_pri
<new_secondary_vv>
60 Migrating Secondary Asynchronous Periodic Remote Copy Volume Groups
keepsnap <primary_vv> <rcpm_group>
name <new_ss_name> <old_ss_name>
3 to the backup system as a disk.