HP 3PAR Operating System Software - Manual (Page 256)

Virtual Volume Migration, the host and source systems remain zoned. Migrating all volumes
requires unzoning the host system from the source system.
The following conditions are required to use Single Virtual Volume Migration:
◦ Both source and destination arrays should be running HP 3PAR OS 3.1.3.
◦ Volumes to be migrated cannot be attached to a Remote Copy relationship.
◦ The host(s) to which the volumes are exported to must be defined using an ALUA persona
on both source and destination arrays.
If any of these requirements are not met, the migration type will require the migration of all
volumes.
•
Minimally Disruptive Migration – Used to migrate virtual volumes that are exported to a host.
This migration type requires shutting down the host system for a short period of time. The
destination system must be running HP 3PAR OS version 3.1.2 or later.
•
Offline Migration – Used to migrate virtual volumes that are not exported to a host. Exported
volumes that you want to migrate must first be unexported to use offline migration. No unzoning
or system shutdown is required.
NOTE: A warning message displays if either of the following licenses is missing:
•
Thin provisioning (needed to create a thin volume)
•
Domain (needed to add the volumes to a domain that is not the <none> domain)
When the migration host exists on the source array, a warning displays indicating to clean it up.
To migrate data:
1. Select Peer Motion in the Manager Pane.
2. In the Common Actions panel, click Migrate Data and the wizard displays.
256 Using Peer Motion in HP 3PAR Management Console Manager