HP EVA to 3PAR StoreServ Online Import Migration Guide (T5494-96571, January 2013)

2 Preparing for data migration
Use the information in this chapter to ensure all necessary tasks are performed and considerations
are understood before beginning a migration.
System requirements
NOTE: For detailed information on ensuring the EVA source and the 3PAR destination are
configured properly for data migration, see the following:
• HP P6000 Enterprise Virtual Array Compatibility Reference. See “Related information”
(page 31) for the document location.
• Single Point of Connectivity Knowledge (SPOCK) website:
http://www.hp.com/storage/spock
Before migrating data from an EVA to a 3PAR storage system using EVA to 3PAR Online Import,
the system environment must meet the following requirements:
• Source EVA storage system must be running a supported firmware level. See the SPOCK
website for supported firmware versions.
• Source EVA storage systems must be managed by Command View 10.2.
• The destination 3PAR storage system must have a Peer Motion license installed.
• The destination 3PAR storage system must be at InForm OS level 3.1.2. or later.
• Source EVA storage systems must have external, not internal, FC switches.
Planning the migration
Advanced planning ensures that you achieve the desired results when migrating data.
• Determine if the migration will involve the minimally disruptive process. If it will, you may want
to plan for brief downtime.
• Identify which virtual disks and hosts will be migrated. If you will not be migrating all the
virtual disks presented to a host, you must unpresent the virtual disks that you do not want
migrated. Otherwise, all the virtual disks will be implicitly included in the migration.
• Determine if you will be using thin or full provisioning on the destination storage system. This
decision impacts the amount of capacity needed on the destination.
• Before starting the migration, you should consider creating a snapshot of each virtual disk
that will be migrated.
• Because there is some impact on performance, you may want to schedule migrations during
off-peak hours, if possible.
• To optimize the rate at which data is migrated from the source, hosts with a lighter load/less
data should be migrated first.
• When selecting objects for migration, be aware of any overlap or sharing of virtual disks
between hosts. The figure below shows a configuration in which there is virtual disk (LUN)
overlap between hosts. In this situation, selecting a host or a virtual disk in any set will result
in every virtual disk and every host in all sets being implicitly selected for migration due to the
overlap.
8 Preparing for data migration