Technical white paper

HP 3PAR Online Import for EMC

Storage (VNX, VNX2, CX, VMAX)

Table of contents
Executive summary ..............................................................................................................................................................3
Features .............................................................................................................................................................................3
Overview of HP 3PAR Online Import for EMC Storage......................................................................................................3
Storage arrays-supported configurations .....................................................................................................................3
HP-supported OS configurations ....................................................................................................................................4
New functionalities and features with OIU 1.4 and HP OS 3.2.2.................................................................................4
HP 3PAR Online Import Utility Architecture .......................................................................................................................4
Storage migration with HP 3PAR Online Import Software ..........................................................................................5
Appliance-less federated data migration ......................................................................................................................5
Storage connectivity (peer connections)........................................................................................................................5
Orchestration tools for HP 3PAR federation technologies ..........................................................................................7
HP 3PAR Online Import ....................................................................................................................................................7
Auto LUN supportnew in OIU 1.4 ................................................................................................................................9
Sub-set volume migrationnew in OIU 1.4 and HP 3PAR OS 3.2.2 ..........................................................................9
SMI-S providerVNX and CX ..........................................................................................................................................9
SMI-S provider VMAX ..................................................................................................................................................... 10
Multipathing support for Windows 2008 and 2012 .................................................................................................. 11
Multipathing support for Windows 2003 .................................................................................................................... 11
Multipathing support for Linux ................................................................................................................................... 11
HP 3PAR Host Personanew in OIU 1.4 .................................................................................................................... 11
Host set and virtual volume setnew in OIU 1.4 ...................................................................................................... 12
Oracle RAC 11g migration ............................................................................................................................................. 12
Best practice for installing MPIO .................................................................................................................................. 13
CLI scripting ..................................................................................................................................................................... 13
HP 3PAR Online Import Utility for EMC Storage installation ......................................................................................... 13
Utility installation ........................................................................................................................................................... 13
Adding users to new user groups ................................................................................................................................ 14
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Migration flow ..................................................................................................................................................................... 14

Prioritization of migrationnew in OIU 1.4 ............................................................................................................... 15
Linux pre-migration flow .............................................................................................................................................. 15
Oracle RAC 11g migration ............................................................................................................................................. 15
Migration setup of multiple source arraysnew in HP 3PAR OS 3.2.2 and OIU 1.4............................................. 16
Monitoring the migration with HP 3PAR System Reporter ........................................................................................... 16
Migration performance ...................................................................................................................................................... 18
Performance enhancements in OIUnew in OIU 1.4 ............................................................................................... 18
EMC to HP 3PAR StoreServ data migration services ..................................................................................................... 18
Frequently asked questions (FAQs) ................................................................................................................................. 18
Terminology ........................................................................................................................................................................ 19

2
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Executive summary
HP 3PAR StoreServ Storage is rapidly being adopted into many IT data centers. With the adoption of the array comes the
need to support a nondisruptive method (where supported by OS) to import data from aging architectures to new HP 3PAR
StoreServ Storage. HP has supported in the past the migration from HP 3PAR StoreServ to HP 3PAR StoreServ using
HP 3PAR Peer Motion technology and EVA to 3PAR StoreServ using HP 3PAR Online Import software as part of the
federated storage movement. HP, in 2014, announced the ability to migrate data from EMC VNX and CX4 arrays to HP 3PAR
StoreServ Storage. Our latest addition to migration support is the EMC VMAX, VNX2, and HDS Universal Storage Platform
arrays, and support for additional HP 3PAR StoreServ Storage. See figure 1 for a list of supported arrays.
Orchestration for HP 3PAR Online Import for EMC Storage is done using a simple, scriptable, command-driven tool titled
HP 3PAR Online Import Utility. The user can migrate virtual disks from an EMC array to an HP 3PAR StoreServ storage
array. This functionality is supported using software present on the HP 3PAR StoreServ array and not be dependent upon
the EMC array, host, or an external appliance for migration. With every new HP 3PAR StoreServ that is purchased, a one-year
license of HP 3PAR Online Import is included at no extra charge. The migration license is built into the HP 3PAR Operating
System (OS) Suite.
Unlike traditional block migrations, HP 3PAR Online Import enables customers to migrate storage volumes from the
source EMC arrays (as defined in figure 1). Migrations (dependent upon operating system) can be online or minimally
disruptive. Migrations can be completed without complex planning or any dependency on extra tools or equipment
connected to a destination HP 3PAR StoreServ Storage array. HP 3PAR Online Import leverages built-in HP 3PAR
StoreServ Thin Technology to power the simple and rapid inline conversion of inefficient, fat volumes on the source
array to more efficient, higher-utilization thin volumes on the destination HP 3PAR StoreServ array.

Features
Provides online or minimally disruptive migration from a supported EMC array to HP 3PAR StoreServ Storage array
Orchestration tool coordinates the movement of data from the source EMC array to the HP 3PAR StoreServ array while
servicing I/O requests from the hosts
Migration can be completed with scriptable CLI
Distinct, defined commands used for migration

Overview of HP 3PAR Online Import for EMC Storage

Storage arrays-supported configurations
HP 3PAR Online Import for EMC Storage supports the following EMC and HP 3PAR StoreServ Storage identifies the arrays.
Table 1 (HP 3PAR Online Import for EMC Storage-supported array configurations), identifies the arrays.
HP 3PAR Online Import for EMC Storage requires HP 3PAR StoreServ operating system 3.1.3 MU1 or later, depending on the
EMC array being migrated. Please check HP SPOCK 1 for a complete list of Host Operating Systems and associated
dependencies, which are needed to support data migration.

Table 1. HP 3PAR Online Import for EMC Storage-supported array configurations

Supported EMC Arrays Supported HP 3PAR StoreServ Arrays

VMAXVMAX SE, VMAX, VMAX 10K/20K/40K HP 3PAR StoreServ 7XX0

CX4120/240/480/960 HP 3PAR StoreServ 8XX0

VNX 5100/5300/5500/5700/7500 HP 3PAR StoreServ 10X00

VNX 5200/5400/5600/5800/7600/8000 HP 3PAR StoreServ 20XX0

1
h20272.www2.hp.com/spock/

3
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

HP-supported OS configurations
Table 2 details supported configurations. For the latest supported configurations and dependencies, the user should refer
to SPOCK. 2 VMAX support begins with HP 3PAR StoreServ OS 3.2.1.

Table 2. Supported OS configurations

Host operating system 3.1.3 MU1 3.2.1 MU2 3.2.2

Windows 2012 X X X

Windows 2008, R2 X X X

Windows 2003, R2 X X X

Hyper V 2008 R2 X X X

RHEL 5.X X X

RHEL 6.X X X X

RHEL 7.X X

Oracle RAC X X

New functionalities and features with OIU 1.4 and HP OS 3.2.2

As the tool matures and new HP 3PAR OS software releases, the OIU tool continues to improve and offer capabilities and
functionalities. The following is a list of the new feature set included as part of OIU 1.4 and HP 3PAR OS 3.2.2.
Auto LUN support
Prioritization of migration tasks
Migration setup of multiple source arrays to single destination array (n:1)
Migration of sub-set volumes
Additional create migration parameters
Persona
VVset
Host set
Additional support of EMC SMI-S provider: Versions and OS
Online Import Utility performance enhancements

The additional functionalities and enhancements are covered in the appropriate sections throughout the paper.

HP 3PAR Online Import Utility Architecture

The HP 3PAR Online Import Utility (OIU) is an application that uses OIU-generated CLI commands to create and monitor the
import activity from an EMC array to an HP 3PAR StoreServ array. The OIU uses HP 3PAR Online Import to move data
transparently from the EMC array to the HP 3PAR StoreServ array online. The OIU uses CLI commands, which can be
summarized in four areas, namely:
Migration creation
Migration start
Migration removal
Migration status

Each of these four areas will be covered separately in the document under the heading Migration commands.

2
h20272.www2.hp.com/spock/

4
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Storage migration with HP 3PAR Online Import Software

HP 3PAR Online Import Software is the engine that migrates block data between a source array and the destination HP 3PAR
StoreServ array without the use of an external appliance or host-based mirroring. The storage arrays involved are
interconnected via dual FC peer links and redundant SAN switches that serve as the dedicated path for the data transfer
between the source and the destination arrays. Depending on the host operating system, the migration of data into the
destination system occurs in either an online, an offline, or a minimally disruptive mode. In the latter case, a shutdown of the
host(s) for a short time is required in order to execute a preparation step for the migration. The actual data transfer occurs
when the host(s) is/are rebooted and their volumes are online. During the migration process, the host OS and all applications
associated with the servers attached to the HP 3PAR StoreServ Storage array remain online and accessible to users.

Appliance-less federated data migration

Appliances brought into the data center, even for brief periods, are a concern for IT managers with respect to security, LAN
and SAN connectivity, power, performance, and management. Many commercial solutions for data migration require the
installation of an appliance that shares SAN bandwidth with other arrays and applications. HP 3PAR Online Import does not
depend on new technology layers or extra tools, nor does it require complex planning. The source and destination arrays
are interconnected via the SAN fabric in a peer fashion using a dedicated set of FC links between them. As a result, there is
no disruption to other SAN traffic or to the Ethernet networking environment during setup, data transfer, and removal of
HP 3PAR Online Import once all migrations are completed.

Storage connectivity (peer connections)

Prior to storage migration, each array is connected to the SAN via normal Fibre Channel protocol. Figure 1 (Storage
connectivity), illustrates connectivity to each independent storage array.
Figure 1. Storage connectivity

Prior to commencement of migration, two additional connections will be made to the HP 3PAR StoreServ array. These
connections are the peer ports in which data will transfer once the migration is initiated. The peer ports are the connection

5
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

ports to the EMC array. Peer ports do not adhere to the practice of using persistent ports. Instead, one port from each node
in a node pair is connected to a single connection on the node.
Figure 2 (Peer connections), illustrates the connection of the peer ports on the array.
Figure 2. Peer connections

Once the peer connections are created, the user can verify connection via the HP 3PAR CLI command showpeer as
illustrated in figure 3 (CLI commands). This figure verifies the connection to the attached HP 3PAR StoreServ. A second
command of showport peer also displays information on the peer port connection. This command displays information
that is specific to the Fibre Channel ports for data migration.
Figure 3. CLI commands

Figure 4 (Data migration), illustrates that once the connections are made and the migration(s) are initiated, data flows from
the EMC array to the HP 3PAR StoreServ array through the peer ports configured on the HP 3PAR StoreServ array. Prior to
migration starting, the path from the EMC to the host is removed. All data flow for the virtual volume being migrated flows
from the EMC array to the HP 3PAR StoreServ array. Data is migrated at this point while the volume is mounted to the host.
The host and all applications can continue to read and write data all through the migration. Data consistency is kept in place
on the EMC array while the migration is in progress. This data consistency allows the user peace of mind knowing that
during the migration of data, should something unforeseen occur, the user can cancel the migration and any data updates
which may have occurred during the migration are still current on the EMC array.

6
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Figure 4. Data migration

After all migrations have completed, the connections to the EMC array through the peer ports are unzoned and all data
traffic is handled by the HP 3PAR StoreServ array.

Orchestration tools for HP 3PAR federation technologies

As part of the HP 3PAR Federation strategy, the following technologies for data migration are available:
HP 3PAR Peer Motion
Data migration technology for online migration from legacy HP 3PAR arrays to current HP 3PAR StoreServ arrays
HP 3PAR Online Import
HP 3PAR Online Import for EVA Storage allows for online data migration of legacy HP EVA Storage arrays to HP 3PAR
StoreServ Storage
HP 3PAR Online Import for EMC Storage allows for online data migration from EMC VNX, 3 EMC CLARiiON CX4, and
EMC VMAX arrays to HP 3PAR StoreServ Storage

HP 3PAR Online Import

Migration with HP 3PAR Online Import from an EMC array is accomplished using the scriptable, command line interface tool
titled HP 3PAR Online Import Utility for EMC Storage. The migration commands issued to the source and the destination
arrays transmit over an out-of-band path, meaning they are outside the data path between the host and the two arrays.

3
See figure 1 for supported EMC arrays

7
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

The granularity for a migration is an entire virtual volume. For an online migration, or minimally disruptive migrations, all
volumes exported to a particular host must migrate in a single data migration instance. The boot volume of a host located
over a SAN on the source EMC array can be migrated to the destination HP 3PAR StoreServ for selected host operating
systems (refer to HP 3PAR Online Migration Guide 4 for complete instructions).
All migration types offer the opportunity to change the volume provisioning from full to thin, or the reverse and select a CPG for
the volumes on the destination system that has different characteristics than the originating RAID type on the source system.
Migration from an EMC array is supported when all hosts and LUNs are contained within the same EMC storage group.
Migration from the selected storage group on the EMC array will migrate data to the designated CPG on the HP 3PAR
StoreServ array. The designation of the CPG is defined at the creation of migration. Subsequently LUNs and hosts can be
implicitly added to a migration, even if they are not specified in the create migration command. When the storage group
selected for migration is identified in the create migration command, the OIU software creates an initiator entry within the
specified EMC storage group. The initiator entry in the EMC storage group is the WWN of the two peer ports on the HP 3PAR
StoreServ array. The EMC array views these entries as host initiators, which allows the migration path to the HP 3PAR
StoreServ array. Because the initiators can only be presented to one EMC storage group at a time, the HP 3PAR Online
Import utility can only migrate one storage group at a time.
Figure 5 (Storage Group migration), illustrates the migration path of the HP 3PAR Online Import from the R&D Storage
Source Group to a destination CPG on the HP 3PAR StoreServ array.
Figure 5. Storage Group migration

For VNX and CX4, each volume or LUN on the EMC storage group is created as a Peer Volume on the HP 3PAR StoreServ
array. Migration of data from the VMAX uses a masking view to create migrations, (Masking view is discussed later in the
paper). A Peer volume has a 1:1 relationship with a storage LUN on the EMC source array. Each Peer volume on the HP 3PAR
StoreServ array is created with RAID 0 protection and the Peer provisioning as the type during the online migration. Each
volume has the same size and name as their counterpart volume on the EMC storage array. Initially, a Peer volume
consumes no space on the destination HP 3PAR StoreServ, but will eventually hold the data from the source EMC array and
become a thin or fully provisioned VV on the destination HP 3PAR StoreServ array with the correct RAID level. Next, OIU
creates an entry for the host under migration in the hosts list on the destination system, and finally exports the volume(s)
from the destination system to the host under migration.

4
h17007.www1.hp.com/us/en/storage/info-library/index.aspx

8
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Online Import moves data in 256 MB blocks. Space for a destination VV is allocated across the physical disks included in the
CPG intended for it. No additional temporary space beyond what is needed for the Peer volumes is allocated on the
destination system during the migration.
Because Online Import is thin aware, data can be converted from a full volume to a thin volume on the fly during the
migration process. The zeroing of blocks is a function of the HP 3PAR StoreServ ASIC(s) which are contained within each of
the nodes on the arrays controller. Thin conversion is a hardware function on the HP 3PAR StoreServ array and not a
software layer as most other storage vendors.
During data migration, all reads by the host from the migrating EMC storage group volumes are served by the source HP 3PAR
StoreServ. Writes by the host go to the destination HP 3PAR StoreServ VVs if the block for volume was previously migrated.
Writes also always go to the source EMC array during the migration to keep them updated in case the migration should halt for
some reason. During the migration the HP 3PAR StoreServ array acts as a proxy array to the EMC storage array.

Auto LUN supportnew in OIU 1.4

The create migration command in OIU 1.4 provided an auto resolve option to solve the issue with LUN conflicts, which
could arise during a migration. A LUN conflict is a conflict whereby the requested LUN number already exists on the
destination HP 3PAR array. This could occur, as an example, if multiple host arrays are migrating to the same HP 3PAR
StoreServ array and each host array contains a LUN 20. This could occur, for example, if multiple host arrays are migrating
to the same HP 3PAR array and each of the host arrays have a LUN 20.
With the auto-resolve option enabled (by default it is set), if any LUN conflict is detected at the destination array, OIU will
automatically assign the next available LUN number.

Sub-set volume migrationnew in OIU 1.4 and HP 3PAR OS 3.2.2

Starting with HP 3PAR OS 3.2.2 and OIU 1.4, users can now migrate a subset of volumes, which are presented to a host from
the source array. The definition of a subset of volumes would be the migration of less than the current volumes presented
to the host on the source array; migration for additional hosts cannot begin until all of the volumes exported to this host
have been fully migrated. An example of a migration of a subset of volumes using a volume-based migration is as follows:
createmigration -sourceuid D0002AC003F -srcvolmap
[{vol1,thin,3par_cpg},{vol2,thin,3par_cpg},{vol3,thin,3par_cpg}, {vol4,thin,3par_cpg}]

Note
All volumes (vol1, vol2, vol3, vol4) should be specified in createmigration command.

startmigration migrationid D0002AC003F subsetvolmap[{vol1,vol2,vol3}]

Expected resultvol1, vol2, vol3 are migrated to destination as a sub-set. The user can trigger an additional
startmigration command to migrate vol4 at a different time interval.

SMI-S providerVNX and CX

The Storage Management Initiative was created to standardize an interoperable storage management technology and
promote this technology to storage, networking, and end user communities. The SMI-S interface defines the functions and
the interfaces to be supported. The SMI-S provider is constantly evolving and newer versions are constantly being updated
to support the fast-changing storage industry. Figure 6 (EMC SMI-S installation), illustrates the completion of the install of
the EMC Solutions Enabler for SMI-S tool.

9
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Figure 6. EMC SMI-S installation

The EMC SMI-S provider is the management interface to the EMC array and the OIU. The SMI-S provider offers detailed
information about the EMC array as well as allows the user to change configuration on the array. The control to set up paths
for migration is a key element in the migration process. The SMI-S provider also is a tool by which the OIU communicates
with the EMC array, and provides access in the selection of volume(s) to be migrated. Figure 7 (SMI-S connection link),
illustrates the architecture of the SMI-S provider.
Figure 7. SMI-S connection link

For the current supported SMI-S provider the user should consult SPOCK and the latest installation documents.

SMI-S provider VMAX

VMAX communication through the SMI-S provider differs from that of the VNX/CX provider although the provider can work
on VNX models as well. The primary driver used in communications is the EMCSMISFCDriver, which communicates to the
backend EMC storage. The EMC CIM Object Manager (ECOM) is packaged within the EMC SMI-S provider, which enables CIM
clients to communicate over HTTP using the SMI-S backend for EMC.

10
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

VMAX storage provisioning is accomplished by setting up the array using the following configuration components:
Initiator grouplogical grouping of Fibre Channel initiators, the group can contain another initiator group for cascading
Port grouplogical grouping of Fibre Channel front-end director ports
Storage groupa logical grouping of up to 4096 Symmetrix devices; LUN addresses are assigned to the devices in the
storage group when the masking view is created using the dynamic LUN addressing feature
Masking viewdefines an association between one initiator group, one port group, and one storage group

Migration of data from the VMAX uses a masking view to create migrations. When the user initiates the command
createmigration, the new masking view contains the following data.
Initiator group, which contains the HP 3PAR StoreServ Peer Port WWNs
Port group, which contain the EMC FC ports
Storage group, which will contain LUNs to be imported to the HP 3PAR StoreServ

Multipathing support for Windows 2008 and 2012

The Native MPIO software solution is designed to utilize all available paths to prevent overloading of any single path and the
accumulation of I/O bottlenecks. MPIO software accomplishes this through a combination of autonomic load balancing, path
failover capabilities, and ease of management.
In the event of a path failure, MPIO routes the data to an alternate path to prevent application disruption. Simple
administration and affordability make MPIO the ideal solution for enhancing performance and reliability in storage
environments.
At the release of the migration tool, HP does not support the EMC PowerPath multipathing solution. The user is required to
remove EMC PowerPath prior to migration of data from EMC to HP 3PAR StoreServ. For Windows installations, MPIO
provider is required during the prestaging of the migration. On Windows hosts, the user modifies the MPIO provider to
include the term 3PARdataVV.

Multipathing support for Windows 2003

HP 3PAR MPIO is needed for use with Windows 2003 systems. Unlike Windows 2008 and 2012, which utilize Native MPIO,
Windows 2003 relies on HP 3PAR DSM for support of Microsoft 2003 Window Servers. HP 3PAR MPIO is a full-featured
DSM for families of disk arrays on Microsoft Windows Server 2003.
HP 3PAR MPIO Software for Microsoft Windows intelligently routes I/O through multiple paths between host and HP 3PAR
Storage Systems for greater availability and load balancing.

Multipathing support for Linux

HP supports the Device-mapper multipath solution for Linux. Device Mapper comes with the Linux installation CD and is
usually installed during the OS installation process. If Device Mapper is not installed, please install it via the installation
manual. Device Mapper multipath configuration file (/etc/multipath.conf) must be edited to configure the HP 3PAR
StoreServ array into the configuration. Within the multipath.conf file, the user must change the vendor to 3PARdata and
the product to VV. Refer to the HP 3PAR StoreServ Online Import for EMC Storage Guide 5 for complete documentation on
configuring multipathing support for Linux.

HP 3PAR Host Personanew in OIU 1.4

Host personas are a set of behaviors that permit hosts connected to the Fibre Channel ports on the HP 3PAR StoreServ
array to deviate from the default host behavior. By assigning a persona to a host, multiple host types, which may have
unique characteristics, can share a single shared port.

5
h17007.www1.hp.com/us/en/storage/info-library/index.aspx

11
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

The createmigration command in OIU 1.4 allows the user to identify the persona type of the host from which data is to be
migrated. An example of the command is as follows:
createmigration -sourceuid 50060160BEA00351 -srchost R65-S02-IG -destcpg FC_r5 -destprov full -migtype MDM
-persona WINDOWS_2008_R2

In this example, we are creating a migration from the EMC source array, on the host R65=S02-IG, migrating to an HP 3PAR
StoreServ array using a RAID 5 CPG. The migration type is a fully provisioned disk and since this is Windows, it is minimally
disruptive. The pesona assigned to the host is Windows 2008 R2. Valid persona types can be displayed from the OIU prompt
by issuing the showpersona command.

Host set and virtual volume setnew in OIU 1.4

Two new parameters were added to the createmigration command with host set and VVset.
Host seta host set VLUN template allows any host that is a member of the host set to see a volume. An example would
be the creation of a host set for MS Exchange Hosts.
Volume seta volume set creates a reference point by which all volumes created in the volume set are presented to all
hosts in the host set. Figure 8 (Host and volume sets), illustrates the concept.
Figure 8. Host and volume sets

Oracle RAC 11g migration

Beginning with HP 3PAR OS 3.2.1 MU2, HP will support the migration of Oracle RAC and a single node database. Host
operating systems using Red Hat Enterprise Linux 6.3 or later can migrate the database if the server is using Native MPIO.
A migration of the database is in a near online mode, the definition of near online refers to zoning changes. If zoning
changes must be made for the migration, those changes could include minimal disruption on the host server. The term
near online refers to zoning changes still must take place for migration and those changes may include some minimal
disruption. HP 3PAR recommends customers test these conditions prior to implementation. If the Linux server is using
PowerPath, then pre-migration steps included in the HP 3PAR Online Import for EMC Storage Data Migration Guide will be
required and disruption to database will occur prior to the migration.
If the Linux server is configured for Native MPIO, online nondisruptive migration of Oracle 11gR2 RAC and single-instance
databases using HP 3PAR Online Import for EMC Storage Data Migration will not require the shutdown of the Oracle
database host.

12
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Best practice for installing MPIO

Removal of EMC PowerPath and installation of MPIO is a two-reboot sequence. The best practice is to shut down all applications
on the server prior to EMC PowerPath removal, and remove EMC PowerPath Software and MPIO; this will require one reboot.
Once the array is restarted, keep all applications offline and install MPIO. It is recommended that the user not reboot after the
addition of MPIO (it will ask you to reboot). The reboot should occur after the start of the migration (this is outlined in detail at
the end of this paper). It is highly recommended that all processes be inhibited from starting on the initial reboot until such time
the migration has begun. Once the migration has begun, normal use of the server can proceed. As mentioned previously in this
paper, the host server(s) can process all I/O while migrating data to the HP 3PAR StoreServ array.

CLI scripting
As part of the HP 3PAR Online Import Utility for EMC Storage, the user can use scripting as part of an automation service to
migrate data from EMC to HP 3PAR StoreServ array. Use the OIUs CLI by executing the HP 3PAR Peer Motion Utility shortcut.
The scripting tool can be used in the following ways:
1. Execute only OIUCLI (as covered in this paper)
2. Execute OIUCLI with parameters

An example of an OIUCLI script is as follows:

java -jar oiucli-1.0.0-jar-with-dependencies.jar -ipaddress localhost -username administrator -password PWD
-script C:/commands.txt

In this example, we have made a call to use init.txt with the OIUCLI. For a complete list of all OIU commands, refer to
HP 3PAR Online Import for EMC Storage Data Migration Guide. Commands are listed under the section HP 3PAR Online
Import Utility for EMC Storage: Commands.

HP 3PAR Online Import Utility for EMC Storage installation

Utility installation
The HP 3PAR Online Import Utility for EMC Storage will be distributed as a free utility to be used with the HP 3PAR Online
Import license. Every new HP 3PAR StoreServ array ships with a built-in 180-day license for the HP 3PAR Online Import with
the HP 3PAR Operating System (OS) Suite. Users can gain access to the HP 3PAR Online Import utility for EMC Storage
software through the HP Software Depot. Installation of the tool allows the user to select an option to install either server,
server/client, or client on an out-of-band host. The server component of the HP 3PAR Online Import Utility for EMC Storage
can be installed on a physical or virtualized host. 6 If the client and server are both installed on the same server, the user only
needs to initiate migration commands on the server on which the tool was installed. If however, for example, the client
software was installed on a laptop and the server software was installed separately on another server, the laptop must
communicate with the server for the migration as illustrated in figure 9 (Installation of OIU plug-in). The server software of
the HP 3PAR Online Import CLI Utility for EMC Storage is used to communicate with the EMC Solutions Enabler (SMI-S).

6
Refer to SPOCK for latest supported configurations

13
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Figure 9. Installation of OIU plug-in

Upon successful completion of the guided installation of the utility, the user should verify that two local groups were added
to the Windows environment. The two new user groups, which are created during the tool installation, are:
HP Storage Migration Admins
HP Storage Migration Users

Adding users to new user groups

After successful installation of the tool, the administrator must add users to at least one of the newly created user groups
as illustrated in figure 10 (Adding users to new user groups).
Figure 10. Adding users to new user groups

Migration flow
The operating system of the migrated host dictates the path by which the user must perform migration tasks. Figure 11
(OIU migration flow), contains the five steps for migration once all pre-work (SMI-S provider, removal of PowerPath, and
zoning) is completed. The decision point after createmigration is if the operating system supports an online upgrade
without reboot or not. Windows Servers will always require a reboot operation to take place prior to the actual start of the
migration; this is due to the need of Windows to rediscover the presented volume.
Some operating systems such as Linux do not need to reboot prior to the start of the migration process. The user is advised
to consult with SPOCK and the current HP 3PAR Online Import for EMC Storage Data Migration Guide for proper migration
steps and plan for a potential reboot.

14
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Figure 11. OIU migration flow

Prioritization of migrationnew in OIU 1.4

In OIU 1.4, the user now has the option to prioritize the migration process. Priority influences when a new import task is
scheduled; tasks with high priority are chosen ahead of medium and low. The priority controls how many parallel moves are
in flight per task.
High priority tasks allow up to six active moves, while Medium and Low only allow four and two moves respectively. The
maximum number of active parallel moves will be capped at 36; this is done to prevent overloading of the array. Mixing is
recommended and will result in higher priority tasks finishing their migration sooner.

Linux pre-migration flow

Whether the user is using Native MPIO or PowerPath, determines which steps prior to migration need to occur. If the user is
using Native MPIO, a change in zoning is all that is required prior to migration. However, if PowerPath is installed and
enabled, PowerPath must first be removed and paths switched on the Device Mapper prior to start of migration. Please
refer to Data Migration Guide for detailed steps and recommendations.

Oracle RAC 11g migration

Beginning with HP 3PAR OS 3.2.1 MU1 and later, HP supports the migration of Oracle RAC and a single-node database on
host operating systems using Red Hat Enterprise Linux 6 Update 5 or later. If the Linux server is running Native MPIO, then
migration of the database can occur near online. The term near online refers to zoning changes that still must take place for
migration and those changes may include some minimal disruption. HP recommends customers test these conditions prior
to implementation. If the Linux server is using PowerPath, then pre-migration steps included in the HP 3PAR Online Import
for EMC Storage Data Migration Guide 7 will be required and disruption to database will occur prior to the migration.
If the Linux server is configured for Native MPIO, online nondisruptive migration of Oracle 11gR2 RAC and single instance
databases using HP 3PAR Online Import for EMC Storage Data Migration will not require the shutdown of the Oracle
database host. For all supported configurations concerning Oracle RAC please refer to SPOCK. 8

7
h17007.www1.hp.com/us/en/storage/info-library/index.aspx
8
h20272.www2.hp.com/spock/

15
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Migration setup of multiple source arraysnew in HP 3PAR OS 3.2.2 and OIU 1.4
As part of HP 3PAR Storage Federation, OIU will support the ability to perform migrations from multiple host arrays to a
single destination HP 3PAR array. Migration from each of the source to destination array is done sequentially. The following
functionality is supported:
Migration from multiple source to single HP 3PAR (up to four sources supported)
Source can be any of the supported arrays: EMC, HDS (all supported versions)
Unidirectional migration only
Destination HP 3PAR array must be at HP 3PAR OS 3.2.2
Simultaneous migrations from multiple source arrays to single destination is not supported
LUN conflicts are resolved at destination using AUTO LUN feature; enabled by default

Monitoring the migration with HP 3PAR System Reporter

HP 3PAR System Reporter software is an easy-to-use, on-node reporting tool, which is integrated within the HP 3PAR
Management Console. The management console provides predefined charts for physical disk usage, ports, AO
configurations, CPGs, VLUNs, virtual volumes, virtual volume sets, controller nodes, and logical disks.
Along with predefined reporting, the management console also provides real-time data reporting for several key areas,
which includes peer migrations. Peer migrations can be viewed by selecting the Peer Motion selection button within the
management panel as shown in figure 12 (Peer Motion migration button).
Figure 12. Peer Motion migration button

The selected button advances the main viewing area to display the peer ports associated with the array in the top half of the
screen. When the user clicks on one of the peer ports the bottom portion of the screen displays exact details of the port
including the transfer rate as shown in figure 13 (Peer Port details). The user can see the connected device WWN illustrated
in the output, which in this case is the EMC array.

16
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Figure 13. Peer Port details

One other section in which you can monitor the live migration is in the section under Performance and Reports button on the
selection bar. Once the menu appears, the user can highlight the storage system they are attached to, select a port (which
displays a drop down) and click Peer Ports. In the main view area a screen similar to figure 14 (Monitoring migrationPeer
Ports) is displayed. This screen is updated once every 30 seconds throughout the migration period. There are only two ports
used for peer migrations. If only one virtual disk is being migrated, then only one of the migration ports is graphed. However, if
more than one virtual disk is being migrated, then the use of both ports will likely be used as illustrated.
Figure 14. Monitoring migrationPeer Ports

17
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Migration performance
As stated and shown in figure 5 (Storage Group migration), the HP 3PAR StoreServ array during the migration phase acts as
a proxy array to the EMC storage array. Any file updates to the source storage volumes passes through the HP 3PAR
StoreServ array Peer Links and on to the EMC array.
Some minor latencies during the migration phase of the HP Online Import for EMC Storage are expected. The read caching
during import phase gives workloads with hotspots better performance, while reducing the workload on the source array.
Some minor latencies on writes to the EMC array during the migration phase are also expected. Best practice is users to
migrate smaller storage groups first, before migrating the larger EMC storage groups. Migrating the smaller storage groups
first minimizes the impact on those groups when the larger groups migrate.

Performance enhancements in OIUnew in OIU 1.4

In OIU 1.4, performance enhancements were included in the tool. The enhancements were added to Local Reads (Peer
Motion), 16 Gb Peer Ports and third-party array plug-in.
To speed up local reads, any data which has been migrated to the destination (HP 3PAR) array will be serviced by the local
array instead of being serviced by the host array (EMC). This avoids the Fibre Channel hop of read access to the EMC array
when data is local.
Support of the current generation for 16 Gb Peer Ports allows for faster migration and load-balancing operations. The tool
is fully interoperable with 8 Gb Peer Ports.
One other enhancement is to provide for quicker scanning of the source array when searching the hosts/LUNs.

EMC to HP 3PAR StoreServ data migration services

HP TS Consulting Data Migration Services helps customers who might desire to explore another method of migrating from
EMC storage to HP 3PAR StoreServ array. Migration services helps free up the resources that would be used for storage
migrations in a very busy environment. The HP TS migration experts using enhanced discovery, pre-planning migration tools
and HP Technical Services Consultants can provide and execute a painless, seamless, and efficient migration strategy. The
enhanced HP Data Migration Services methodologies and technologies also allow HP to provide our customers cost-effective,
advanced storage migration services that are highly successful throughout the storage industry.
To enlist the services of HP TS migration experts, consult with your local HP Sales representative or contact them through
the following link hp.com/us/en/business-services/it-services.html?compURI=1078608.

Frequently asked questions (FAQs)

Q. What is the minimum version of HP 3PAR OS for migrations from EMC arrays?
A. The array must be running HP 3PAR OS 3.1.3 MU1 or later, 3.2.1 MU1 or later for VMAX, and 3.2.2 or later for VNX2.
Q. If I am running HP 3PAR OS 3.1.3 can I still use the tool to migrate?
A. No, testing has shown that unpredictable results can occur which may result in an outage; you should upgrade to
3.1.3 MU1.
Q. Which Fibre Channel HBAs/FC Switches can be used for migrations?
A. Please refer to HP SPOCK for supported configurations or ask the Solutions Architect assigned to your account.
Q. How do I access HP SPOCK?
A. Please direct your browser to the following URL: h20272.www2.hp.com/spock.

18
Technical white paper | HP 3PAR Online Import for EMC Storage (VNX, VNX2, CX, VMAX)

Q. Is the OIU tool licensed?

A. No, the tool is provided free of charge by HP for one year.
Q. Are there logs files kept on the system with reference to the results of the migration?
A. C:\Program Files (x86)\Hewlett-Packard\hp3paremcoiu\OIUTools\tomcat\32-bit\apache-tomcat-7.0.37
\logs\hp3paremc.log.
Q. Are error messages explained in any documentation?
A. Yes, refer to the HP 3PAR Online Import for EMC Storage Data Migration Guide.
Q. Does HP offer data migration services that include Online Import for EMC?
A. Yes, HP TS Consulting can provide customers data migration services to complete a full storage transformation to
HP 3PAR Storage.
Q. Which port numbers are used for communications with the HP 3PAR OIU?
A. Default port numbers for EMC to HP 3PAR:

Server Port: 2396

Shutdown Port: 2397

Terminology
HP
MCManagement Console
SPService Processor
VSPVirtual Service Processor
OIUOnline Import Utility
SMI-SStorage Management Imitative Software
MDMMinimally Disruptive Migration
VVVirtual Volume
CPGCommon Provisioning Group

EMC
SGStorage Group
FASTFully Automated Storage Tiering
SPStorage Processor: Controller
CSControl Station

Learn more at
hp.com/go/3PAR

Sign up for updates

hp.com/go/getupdated Share with colleagues Rate this document

Copyright 20142015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should
be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft, Windows, and Windows Server are either registered trademarks
or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle and/or its affiliates. Red Hat is a
registered trademark of Red Hat, Inc. in the United States and other countries.

4AA5-2802ENW, September 2015, Rev. 3