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

1 Overview of HP EVA to 3PAR StoreServ Online Import
HP EVA to 3PAR StoreServ Online Import manages the migration of data from a source EVA storage
system to a destination 3PAR storage system. Using HP EVA to 3PAR StoreServ Online Import, you
can migrate EVA virtual disks and host configuration information to a 3PAR destination storage
system without changing host configurations or interrupting data access.
HP EVA to 3PAR StoreServ Online Import coordinates the movement of data from the source while
servicing I/O requests from the hosts. During the data migration, host I/O is serviced from the
destination 3PAR storage system. The host/virtual disk presentation implemented on the EVA is
maintained on the 3PAR destination.
How HP EVA to 3PAR StoreServ Online Import works
The following information provides an overview of the steps involved in the HP EVA to 3PAR
StoreServ Online Import data migration.
Online data migration
1. The host is connected (zoned) to the source EVA storage system where its volumes reside.
2. A destination 3PAR storage system is connected (zoned) to the source EVA. The 3PAR storage
system is configured as a new host on the source EVA. All of the volumes exported to the
original host are exported to the 3PAR.
3. The 3PAR storage system "admits" these volumes, which creates a set of peer volumes that
are fully backed by the data on the EVA.
4. The host is connected (zoned) to the destination 3PAR storage system. The admitted volumes
on the 3PAR are now exported (presented) to the host.
5. The host performs the appropriate SCSI rescan/multipathing reconfiguration to detect the
exported volumes from the 3PAR storage system. The exported volumes are detected as
additional paths to existing EVA LUNs.
6. Once the host detects the paths to the 3PAR storage system, the host connections to the EVA
can be unzoned. The host retains access to all its data through the 3PAR connections, which
are now the only paths to the host data.
7. The 3PAR storage system begins copying data from the EVA to local storage on the 3PAR
storage system. During this process, the 3PAR continues to mirror writes to the EVA, so the
EVA retains a consistent copy of the data on the volumes being migrated. Once the 3PAR
storage system has copied all the data on a volume to local storage, it stops mirroring writes
to the EVA for that volume. The volume is now a normal local volume on the 3PAR storage
system.
8. When all of the host volumes have been copied to the 3PAR storage system, the migration is
complete. The exports from the EVA to the 3PAR storage system and the host can now be
removed.
9. If no additional migrations are to be performed, the zoning between the source EVA and the
destination 3PAR storage system can now be removed.
10. The HP EVA to 3PAR StoreServ Online Import will create a 3PAR volume matching the geometry
of the EVA LUN using SCSI mode sense data and the respective number of sectors/heads.
The 3PAR default is 304 sectors and 8 heads. While most operating systems do not use the
mode sense geometry data, the online import matches the geometry of the migrated volume
to ensure that expected volume characteristics are seen on the 3PAR side.
Minimally disruptive data migration
1. The host is connected (zoned) to the source EVA storage system where its volumes reside.
How HP EVA to 3PAR StoreServ Online Import works 5