HP 3PAR Peer Motion Guide

A Peer Motion in a Remote Copy Environment
Peer Motion allows the seamless migration of data from a legacy system to a modern array. Use
the following procedures when migrating both primary and secondary storage Remote Copy
volumes to a new system using Peer Motion.
NOTE: When configuring Peer Motion, it may be necessary to make modifications to the FC
switch because the WWNs will change when moving from peer to host modes. Peer Motion
provides the same LUN for new volume that was presented by the old volume.
Migration of a Primary System
Migrating from A to C, where A is currently in a Remote Copy group with B, the following scenario
is envisaged:
1. importvv begins the migration from A to C. Because all writes are passed onto A, Remote
Copy to B can continue without any changes.
2. Once importvv has completed, it blocks I/O to A automatically, and provides us with
snapshot of the original base volume, A.
a. In a synchronous RC system, A->B should be fully synced. In a periodic system, it will
require a final re-sync to ensure volumes are mirrored.
3. At this point, the secondary volume, B, can be admitted to a Remote Copy Group with the
imported volume C, and the Remote Copy relationship can resume, with minimal downtime
and disruption.
Figure 14 Primary system migration
Detailed instructions
A) Old Primary: <old_primary_vv>
B) Secondary: <secondary_vv>
C) New Primary: <new_primary_vv>
Assuming an existing RC relationship between A and B:
1. On new array C: Bring the ports online, where n:s:p is the port address for the FC ports.
N.B: Peer Motion needs two FC ports.
• controlport offline -f n:s:p
• controlport config peer -ct point n:s:p
2. On old array A: Set FC ports to host. Configure the new array as a host and export the original
primary vlun to the new host (C). For each FC port to the host:
Migration of a Primary System 85