HP EVA-to-3PAR Online Import Migration Guide

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 host.
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 cleanly shutdown and unzoned from the source EVA.
5. The 3PAR storage system begins copying data from the EVA to local storage on the 3PAR
storage system. No writes of new data will be made to the 3PAR storage system or the EVA
while the host is shutdown. Data from the EVA is written to the 3PAR storage system once the
import process begins.
6. Once the 3PAR storage system has started copying the data the host is zoned to the destination
3PAR array and brought back up. The host is now accessing its data via the destination 3PAR
while the migration of data from the EVA continues.
7. The 3PAR storage system continues to mirror writes to the EVA, so the EVA retains a consistent
copy of the data on the volumes being migrated.
8. 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.
9. 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.
10. If no additional migrations are to be performed, the zoning between the source EVA and the
destination 3PAR storage system can now be removed.
Types of data migration
HP EVA to 3PAR StoreServ Online Import supports three types of data migration. See the SPOCK
documentation for information on the type of migration that must be used.
• Online— During online migration, all presentation relationships between hosts and virtual
disks being migrated are maintained. Host I/O to the data is not disrupted during an online
migration.
• Offline— Selected when migrating one or more unpresented virtual disks. During offline
migration, only the selected virtual disks are migrated. No hosts are migrated in this situation.
• Minimally disruptive— The host multipath solution used to access the storage system must be
reconfigured from the one that is currently in use for the EVA to a solution that is supported
with the destination 3PAR storage system. Host I/O is interrupted only during the time it takes
to reconfigure the host. For more information, see “Reconfiguring the Windows host DSM”
(page 10).
Understanding what data is migrated
Data migration can be done by selecting a host or a virtual disk on the source EVA. In addition
to the host or virtual disk explicitly selected for migration, other objects may be included in the
migration using implicit selection. A pre-migration process identifies the relationship between hosts
and presented virtual disks and selects all necessary objects to completely migrate the hosts.
Consequently, the explicit selection can lead to many implicit selections and a large amount of
data being migrated. For example, selecting a single host will result in the migration of the host,
any virtual disks presented to it, any additional hosts to which those virtual disks are presented,
and any virtual disks presented to those hosts.
IMPORTANT: The implicit selection of objects for migration cannot be modified. If the number
of objects selected for migration becomes too large, the user has the option of canceling the
migration before it is started. Once a migration begins, it cannot be stopped.
6 Overview of HP EVA to 3PAR StoreServ Online Import