HP EVA-to-3PAR Online Import Migration Guide (T5494-96577)

Local replication
• Any sharing relationships among snapshots and mirrorclones are lost during migration.
Snapshots become standalone objects on the destination 3PAR storage system. Mirrorclones
cannot be migrated.
Remote replication
• If the source EVA storage system is using HP Continuous Access data replication, virtual disks
that are in data replication relationships cannot be migrated. To migrate a virtual disk in a
data replication relationship, stop the replication and migrate the virtual disk. When migration
is complete, you can use Remote Copy on the 3PAR storage system to recreate the original
remote replication structure between 3PAR storage systems.
Reconfiguring the Windows host DSM
When migrating a Windows host, a minimally disruptive migration process is used. This involves
reconfiguring the host DSM used to communicate with the storage system from an EVA DSM to a
3PAR DSM.
After the migration preparation phase is complete, the Windows host must be shut down and
reconfigured to use the native Microsoft MPIO DSM (Windows 2008, 2008R2, 2012) or the 3PAR
DSM (Windows 2003). Contact your local HP representative for information on acquiring the HP
3PAR MPIO DSM for Windows.
NOTE: When reconfiguring a host to use the native Microsoft MPIO DSM on Windows 2008
or Windows 2012, use 3PARdataVV as the device hardware ID.
The data transfer migration phase is then started, and the host is brought back online. This process
ensures that the Windows host is never multipathing between the source EVA and the destination
3PAR. Even if the native Microsoft MPIO DSM is already configured on Windows 2008 or Windows
2012, it is necessary to restart the host after unzoning the source EVA from host.
IMPORTANT: If you unzone the host and EVA but don't reconfigure the host DSM, the host/cluster
will experience an outage because it will not be able to communicate with the destination 3PAR
storage system.
Preparing Windows clusters for migration
When migrating Windows clusters, the cluster must first be disabled so that any SCSI reservations
in use are released. For Windows 2003 and 2008 clusters, this can be achieved by stopping all
applications running on the cluster, then stopping the cluster service on ALL nodes (For more
information, see Microsoft's documentation on how to start/stop the cluster services).
When migrating a Windows Server 2012 cluster, maintenance mode must be set on the cluster
disks to clear SCSI reservations on the disks. Because the quorum disk cannot be set in the
maintenance mode, it must be set to the offline mode to clear the SCSI reservations. Then, the
cluster service must be stopped on ALL nodes.
NOTE: If a Windows host selected for migration (either explicitly or implicitly) is a member of a
cluster, all of the remaining hosts in the cluster will be added to the migration implicitly.
Network and fabric zoning requirements
Data migration requires the necessary zoning to create paths between the source and destination
storage systems and any hosts involved in the migration. The data paths used are shown in Figure 1
(page 11).
• Two unique paths must be zoned between the source and destination storage systems. To
create two paths, the two controller ports on the source EVA must be connected to two peer
10 Preparing for data migration