HP 3PAR Peer Motion Guide

1 Overview of HP 3PAR Peer Motion
HP 3PAR Peer Motion provides the non-disruptive migration of a host and its data from a source
storage system to a destination storage system, with I/O requests from all attached hosts continuing
to be serviced throughout the migration process. Virtual volumes and system configuration
information can be copied to a new system with no changes to host configurations, no loss of
access by a host to its data in an online migration, and a minimal downtime during a minimally
disruptive migration.
The Peer Motion process can be orchestrated using the HP 3PAR Management Console, which
runs on a Windows or Linux management host. This host must have management network
connectivity to both the source and destination systems, but does not need any access to the data
being migrated. For more information see, “Using Peer Motion in HP 3PAR Management Console
Manager” (page 18).
The Peer Motion process can also be orchestrated using the HP 3PAR Peer Motion Utility, which
can be used for single virtual volume and Online Windows Cluster migrations with the use of
scripting commands. For more information, see “Using the HP 3PAR Peer Motion Utility ” (page 60).
NOTE: Peer Motion with the HP 3PAR Management Console is supported when the destination
system is running HP 3PAR OS 3.1.2 or a later version. If the destination system is running HP
3PAR OS 3.1.1, refer to the HP 3PAR Peer Motion Manager 1.1.0 Software User's Guide.
Peer Motion with the HP 3PAR Peer Motion Utility is supported when the destination system is
running HP 3PAR OS 3.1.1 or a later version.
Migration Types
There are three types of data migration:
• Online — With online migration, there is no disruption to the hosts and the data accessed by
the hosts remains available throughout the migration process. The destination system
non-disruptively moves the volumes from the source system and completes the migration while
servicing I/O requests from the hosts.
◦ Host Level Migration — If the source system is running HP 3PAR OS 3.1.2 or earlier and
the destination system is running HP 3PAR OS 3.1.3 or later, then all the volumes exported
to the host from the source system must be migrated to the destination system, and the
host must be unzoned from the source system before the migration begins.
◦ Single Volume Migration — If the source system is running HP 3PAR OS 3.1.3 or later
and the destination system is running HP 3PAR OS 3.1.3 or later, then a subset (one or
more) of the volumes exported to the host can be migrated to the destination system. The
host does not need to be unzoned from the source system during the migration process;
it can concurrently access the volumes that have not been migrated from the source system
and the volumes that are in the process of, or have migrated to the destination system.
• Minimally Disruptive Migration — With Minimally Disruptive Migration (MDM), there is a
temporary short duration disruption, as the host is removed from the source system, then
reconfigured to use the destination system. However, the host is able to access the data through
the destination system while data migration from the source to destination is occurring.
• Offline — With offline migration, volumes are not actively exported, and there is no access
to the data throughout the migration process. The volumes can be exported any time after the
migration ends using the HP 3PAR OS export commands.
For a list of support host OS for single VV migration, refer to SPOCK at:
http://www.hp.com/storage/spock.
6 Overview of HP 3PAR Peer Motion