HP 3PAR Peer Motion Guide

• admitvv RCNewSecVV:50002AC003E80091
• importvv -tpvv -snap @vvname@.ro -snp_cpg cpg_pri cpg_pri
<new_secondary_vv>
6. On A, restart the group. You do not have to wait for the importvv to complete.
• startrcopygroup RCPM_Group
7. At this point, maintain a full primary->secondary relationship for the duration of the import,
minimizing downtime. Once the Peer Motion migration completes, stop and delete the Remote
Copy group. NB, when RC Groups are removed, all associated snapshots are removed with
it (why the earlier copy was made).
• stoprcopygroup RCPM_Group
• removercopygroup RCPM_Group
8. Create new RC target (in this case RCIP):
• creatercopytarget C IP n:s:p:10.100.37.164
• creatercopygroup New_PM_group C:periodic
• admitrcopyvv <primary_vv> New_PM_group C:<new_secondary_vv>
9. Start the new group
• startrcopygroup New_PM_group <primary_vv>:RCPM_ResumeSS.ro
• showrcopy
The new system should be up and running.
NOTE: The following only affects synchronous groups: There are potential corner cases which
may result in miss compares occurring between the primary and the new secondary, such as if the
snapshots are not exact, due to I/Os not being propagated to the secondary after the RC group
stops. However, the planned feature of user initialized synchronous snapshots between the two
systems will mitigate this risk.
88 Peer Motion in a Remote Copy Environment