HPE 3PAR Online Import for EMC Storage Importing EMC Storage VNX, VNX2, CX4, VMAX

Contents Executive summary ................................................................................................................................................................................................................................................................. 3

Features ............................................................................................................................................................................................................................................................................................. 3

Overview of HPE 3PAR Online Import for EMC Storage ...................................................................................................................................................................... 3

EMC Storage arrays-supported configurations ...................................................................................................................................................................................... 3

HPE-supported Host Operation System configurations ................................................................................................................................................................ 4

New functionalities and features with OIU 1.5 and HPE 3PAR Operating System 3.2.2 and above .................................................... 4

HPE 3PAR Online Import Utility architecture ................................................................................................................................................................................................. 4

Storage migration with HPE 3PAR Online Import Software ....................................................................................................................................................... 5

Appliance-less federated data migration...................................................................................................................................................................................................... 5

Storage connectivity (peer connections)...................................................................................................................................................................................................... 5

Orchestration tools for HPE 3PAR Federation technologies............................................................................................................................................................ 7

HPE 3PAR Online Import Utility ........................................................................................................................................................................................................................... 8

Supported HPE 3PAR Online Import Utility Migrations ................................................................................................................................................................. 8

Storage Management Initiative Specification Provider .......................................................................................................................................................................... 8

EMC Solutions Enabler .................................................................................................................................................................................................................................................. 9

EMC SMI-S Provider......................................................................................................................................................................................................................................................... 9

EMC CX/VNX/VNX2 ........................................................................................................................................................................................................................................................ 9

EMC VMAX .......................................................................................................................................................................................................................................................................... 10

SMI-S Client.......................................................................................................................................................................................................................................................................... 10

Data migration ......................................................................................................................................................................................................................................................................... 10

EMC CX/VNX/VNX2 .................................................................................................................................................................................................................................................... 10

VMAX ........................................................................................................................................................................................................................................................................................ 10

Technical white paper

Technical white paper

Multipathing support ......................................................................................................................................................................................................................................................... 11

Microsoft Windows Server 2008 and 2012 .......................................................................................................................................................................................... 11

Microsoft Windows Server 2003 ...................................................................................................................................................................................................................... 11

Multipathing support for Linux base OS ................................................................................................................................................................................................... 11

Veritas Dynamic Multipathing ............................................................................................................................................................................................................................ 12

Best practice for installing Windows MPIO ............................................................................................................................................................................................. 12

Some features of OIU ........................................................................................................................................................................................................................................................ 12

HPE 3PAR Host Persona ........................................................................................................................................................................................................................................ 12

Host set and virtual volume set......................................................................................................................................................................................................................... 12

Oracle RAC 11g migration ..................................................................................................................................................................................................................................... 13

Prioritization of migration ....................................................................................................................................................................................................................................... 13

Migration of multiple source arrays ............................................................................................................................................................................................................... 13

CLI scripting......................................................................................................................................................................................................................................................................... 13

HPE 3PAR Online Utility installation and migration ............................................................................................................................................................................. 14

HPE 3PAR Online Import Utility installation ......................................................................................................................................................................................... 14

Migration flow .................................................................................................................................................................................................................................................................... 15

Monitoring the migration ........................................................................................................................................................................................................................................ 15

Using HPE 3PAR StoreServ Management Control System Reporter (2.3 and above) to monitor migration........................... 16

Monitoring migration with HPE 3PAR CLI .............................................................................................................................................................................................. 17

Migration performance .................................................................................................................................................................................................................................................... 17

Performance enhancements in HPE 3PAR OIU 1.5 ....................................................................................................................................................................... 17

Technical white paper Page 3

Executive summary HPE 3PAR StoreServ Storage is rapidly being adopted into many IT data centers. With the adoption of the array comes the need to support a non-disruptive method (where supported by OS) to import data from aging architectures to new HPE 3PAR StoreServ Storage. Hewlett Packard Enterprise has supported in the past the migration from HPE 3PAR StoreServ to HPE 3PAR StoreServ using HPE 3PAR Peer Motion technology and EVA to HPE 3PAR StoreServ using HPE 3PAR Online Import for EVA software as part of the federated storage movement. HPE, in 2014, announced the ability to migrate data from EMC VNX and CX4 arrays to HPE 3PAR StoreServ Storage. Our latest addition to migration support is the EMC VMAX, VNX2, IBM XIV, and HDS Universal Storage Platform arrays, and support for additional HPE 3PAR StoreServ Storage. See figure 1 for a list of supported arrays.

Orchestration for HPE 3PAR Online Import for EMC Storage is done using a simple, scriptable, command-driven tool titled HPE 3PAR Online Import Utility. The user can migrate virtual disks from an EMC array to HPE 3PAR StoreServ Storage. This functionality is supported using software present on the HPE 3PAR StoreServ and not be dependent upon the EMC array, host, or an external appliance for migration. With every new HPE 3PAR StoreServ that is purchased, a one-year license of HPE 3PAR Online Import is included at no extra charge. The migration license is built into the HPE 3PAR Operating System (OS) Suite.

Unlike traditional block migrations, HPE 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 HPE 3PAR StoreServ Storage. HPE 3PAR Online Import leverages HPE 3PAR StoreServ Thin Built In 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 HPE 3PAR StoreServ.

Features • Provides online or minimally disruptive migration from a supported EMC array to HPE 3PAR StoreServ Storage array

• Orchestration tool coordinates the movement of data from the source EMC array to the HPE 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 HPE 3PAR Online Import for EMC Storage EMC Storage arrays-supported configurations HPE 3PAR Online Import for EMC Storage supports the following EMC and HPE 3PAR StoreServ Storage arrays. Currently supported EMC configurations include the following.

Table 1. Supported EMC arrays for migration

EMC CX4 model number EMC VNX model number EMC VNX2 model number EMC VMAX model number

CX4-120 VNX5100 VNX5200 VMAX

CX4-240 VNX5300 VNX5400 VMAX SE

CX4-480 VNX5500 VNX5600 VMAX 10K

CX4-960 VNX5700 VNX5800 VMAX 20K

VNX7500 VNX7600 VMAX 40K

VNX8000

Technical white paper Page 4

HPE 3PAR Online Import for EMC Storage requires HPE 3PAR StoreServ operating system 3.1.3 MU1 or later, depending on the EMC array being migrated. Check HPE SPOCK1 for a complete list of Host Operating Systems and associated dependencies, which are needed to support data migration.

HPE-supported Host Operation System configurations Refer to the HPE SPOCK reference at the bottom of the preceding page for supported HPE 3PAR Online Import for EMC Storage Host Operating System Support Matrix.

New functionalities and features with OIU 1.5 and HPE 3PAR Operating System 3.2.2 and above As the tool matures and new HPE 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.5 and HPE 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

HPE 3PAR Online Import Utility architecture The HPE 3PAR Online Import Utility (OIU) is an application that uses CLI commands to create and monitor the import activity from an EMC array to an HPE 3PAR StoreServ. The OIU uses HPE 3PAR Online Import to move data transparently from the EMC array to the HPE 3PAR StoreServ 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.”

1 hpe.com

Technical white paper Page 5

Storage migration with HPE 3PAR Online Import Software HPE 3PAR Online Import software is the engine that migrates block data between a source array and the destination HPE 3PAR StoreServ 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 HPE 3PAR StoreServ Storage 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. HPE 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 HPE 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. The HPE 3PAR Storage array and the source array are interconnected via dual FC Peer links.

Using dedicated paths (peer ports) allows for seamless, non-interruptible, one-direction data movement between the EMC source and the HPE 3PAR destination arrays.

Peer port connections on the HPE 3PAR array do not adhere to the practice of using persistent ports, instead, one port from each node in the node pair is connected to the each side of the fabric. The ports do not need to be on adjacent ports but must be in the same node pair. As an example, user/admin could assign a peer port to Node 0: Slot 1: Port 1: on one node in the cluster pair and on the adjacent node, the peer port (as an example) on Node 1: Slot 1: Port 4.

The assignment of peer ports can be accomplished using the cli% command controlport config peer -ct point 0:1:1, this uses the example cited above using Node 0: Slot 1: Port 1: as a peer port. A simple diagram of peer port connection is illustrated in figure 1 below.

Figure 1. Peer port connection overview

Technical white paper Page 6

Additionally the user may choose to create the peer ports using the HPE 3PAR StoreServ Management Console (SSMC) as shown in figure 2. The user would select a port by using the drop-down from the HPE 3PAR SSMC “Main Menu” and selecting “Ports.” Once selected, all ports are shown in the user’s main screen; the user would select a port and edit the port from the “Actions” drop-down. In the example, any setting contained within the box can be modified by selecting an object from each drop down within the objects box.

Figure 2. Peer port selection using HPE 3PAR SSMC

Once the peer connections are created, the user can verify the connection via the cli% command showpeer as illustrated in figure 3. This figure illustrates the connection to the attached HPE 3PAR StoreServ. A second cli% 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. Display peer connections

Technical white paper Page 7

Figure 4 illustrates that once the connections are made and the migration(s) are initiated, data flows from the EMC array to the HPE 3PAR StoreServ Storage through the peer ports configured on the HPE 3PAR StoreServ Storage. 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 HPE 3PAR StoreServ Storage. 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.

Figure 4. Fabric connections during migration

Orchestration tools for HPE 3PAR Federation technologies As part of the HPE 3PAR Federation strategy, the following technologies for data migration are available:

• HPE 3PAR Peer Motion

– Data migration technology for online migration from legacy HPE 3PAR StoreServ Storage to current HPE 3PAR StoreServ

• HPE 3PAR Online Import

– HPE 3PAR Online Import for EVA Storage allows for online data migration of legacy HPE EVA Storage to HPE 3PAR StoreServ Storage

– HPE 3PAR Online Import Utility (OIU) for EMC Storage allows for online data migration from EMC VNX2, EMC CLARiiON CX4, and EMC VMAX arrays to HPE 3PAR StoreServ Storage

– Additionally HPE 3PAR supports Online Import of HDS and IBM XIV arrays. For a complete list of supported configurations the user should consult HPE SPOCK

Technical white paper Page 8

HPE 3PAR Online Import Utility Migration with HPE 3PAR Online Import from an EMC array is accomplished using the scriptable, command line interface tool titled “HPE 3PAR Online Import Utility.” 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. 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 HPE 3PAR StoreServ for selected host operating systems. For a list of all currently supported host operating systems, refer to HPE SPOCK.

All migrations offer the user the opportunity to change volume aspects during the migration. As an example the volume which currently resides on the EMC is 200 GB fully provisioned RAID 5 volume. The user decides to save space and, during migration, changes the volume from fully provisioned to thinly provision and the RAID type from 5 to 6. The aspects of the volume are changed once it is written on the HPE 3PAR array. The change of volume aspect is calculated and modified on the HPE 3PAR StoreServ as the data is being copied.

Supported HPE 3PAR Online Import Utility Migrations Migration implementation setup is largely dependent upon the type of the EMC array. Currently supported EMC arrays offer two types of migration configurations. Currently supported CX, VNX, and VNX2 arrays use the Storage Group as the source for the migration. VMAX arrays use the association with the following groups (Initiator, Port, and Storage Group) to create the Masking View. The Masking View is used as the source for the storage migration from a VMAX. The following sections detail the movement of the data from an EMC array to HPE 3PAR StoreServ Storage.

Storage Management Initiative Specification Provider The Storage Management Initiative (SMI-S) 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.

The EMC SMI-S Provider is the management interface to the EMC array and the HPE 3PAR Online Import Utility. 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 HPE 3PAR OIU communicates with the EMC array, and provides access in the selection of volume(s) to be migrated.

Technical white paper Page 9

The following illustration in figure 5 is used as we discuss each of the components.

Figure 5. SMI-S provider components

EMC Solutions Enabler The EMC Solutions Enabler provides the process to manage groups of host initiators, front-end ports, and storage volumes on the EMC storage frame. Device groups are user-defined objects that are used to view and manage groups within the EMC array. Use of the EMC Solutions Enabler provides information for migration management. Refer to “HPE 3PAR Peer Motion and HPE 3PAR Online Import User Guide,”2

EMC SMI-S Provider 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 5 illustrates the architecture of the SMI-S Provider.

EMC CX/VNX/VNX2 The SMI-S Provider provides the basic interface to the CX and VNX arrays. When the SMI-S Provider is running, it automatically discovers the EMC storage arrays connected to the fabric. The SMI-S Provider discovers CLARiiON and VNX storage arrays using the following discovery methods.

• In-band discovery—the array is discovered when attached to fabric automatically

• Out-of-band—it can discover array without be attached to a host

2 h20564.www2.hpe.com/hpsc/doc/public/display?docId=c04783896

Technical white paper Page 10

EMC VMAX EMC 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.

SMI-S Client Initially providing a foundation for identifying the attributes and properties of storage devices, SMI-S now also delivers services such as discovery, security, virtualization, performance, and fault monitoring.

The SMI-S client software includes:

• Configuration discovery

• Provisioning

• Security

• Asset management

• Event management

Data migration EMC CX/VNX/VNX2 For VNX and CX4, each volume or LUN on the EMC storage group is created as a Peer Volume on the HPE 3PAR StoreServ Storage. 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 HPE 3PAR StoreServ Storage 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 HPE 3PAR StoreServ, but will eventually hold the data from the source EMC array and become a thin or fully provisioned VV on the destination HPE 3PAR StoreServ Storage with the correct RAID level. Next, HPE 3PAR 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.

HPE 3PAR 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 HPE 3PAR StoreServ ASIC(s) which are contained within each of the nodes on the arrays controller. Thin conversion is a hardware function on the HPE 3PAR StoreServ and not a software layer unlike most other storage vendors.

During data migration via the HPE 3PAR OIU, all reads by the host from the migrating EMC storage group volumes are served by the destination HPE 3PAR StoreServ. Writes by the host go to the destination HPE 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 HPE 3PAR StoreServ Storage acts as a proxy array to the EMC storage array.

VMAX EMC VMAX storage provisioning is accomplished by setting up the array using the following configuration components:

• Initiator group—logical grouping of Fibre Channel initiators, the group can contain another initiator group for cascading

• Port group—logical grouping of Fibre Channel front-end director ports

• Storage group—a logical grouping of up to 4096 Symmetric 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 view—defines an association between one initiator group, one port group, and one storage group

Technical white paper Page 11

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 HPE 3PAR StoreServ Peer Port WWNs

• Port group, which contain the EMC FC ports

• Storage group, which will contain LUNs to be imported to the HPE 3PAR StoreServ

Multipathing support Microsoft Windows Server 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, Hewlett Packard Enterprise does not support the EMC PowerPath multi-pathing solution. The user is required to remove EMC PowerPath prior to migration of data from an EMC storage array to HPE 3PAR StoreServ. The MPIO provider is required during the prestaging of the migration. On the Microsoft® Windows® hosts, the user modifies the MPIO provider to include the term “3PARdataVV.”

Microsoft Windows Server 2003 HPE 3PAR MPIO is needed for use with Windows 2003 systems. Unlike Windows 2008 and 2012, which utilize native MPIO, Windows 2003 relies on HPE 3PAR DSM for support of Microsoft 2003 Window Servers. HPE 3PAR MPIO is a full-featured DSM for families of HPE 3PAR disk arrays on Microsoft Windows Server® 2003.

HPE 3PAR MPIO Software for Microsoft Windows Server 2003 intelligently routes I/O through multiple paths between host and HPE 3PAR Storage Systems for greater availability and load balancing.

Multipathing support for Linux base OS Hewlett Packard Enterprise supports the Device Mapper multipath solution for Linux®:

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

Refer to HPE SPOCK “HPE 3PAR Online Import for EMC, HDS, and IBM–Migration Host Support Matrix” for supported configurations of multipathing software or configurations.4

3 http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c04783896 4 spock.corp.int.hpe.com/spock/utility/document.aspx?docurl=shared%20documents/sw/array_3par/3par_online_import_hs_emc_hds_ibm.2016_06_08.pdf

Technical white paper Page 12

Veritas Dynamic Multipathing HPE 3PAR OIU supports using Veritas Dynamic Multipathing (DMP) for Linux-based hosts. Refer to HPE SPOCK “HPE 3PAR Online Import for EMC, HDS, and IBM—Migration Host Support Matrix” for supported configurations of multipathing software or configurations as noted above for current supported versions.

Best practice for installing Windows MPIO Removal of EMC PowerPath and installation of native 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 native MPIO. It is recommended that the user not reboot after the addition of native MPIO (it will ask you to reboot). The reboot should occur after the start of the migration. 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 Host Server can proceed. As mentioned previously in this paper, the host server(s) can process all I/O while migrating data to the HPE 3PAR StoreServ Storage.

Some features of OIU HPE 3PAR Host Persona Host personas are a set of behaviors that permit hosts connected to the Fibre Channel ports on the HPE 3PAR StoreServ Storage 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.

The “createmigration” command in OIU 1.5 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 HPE 3PAR StoreServ Storage using a RAID 5 CPG. The migration type is a fully provisioned disk and since this is Windows, it is minimally disruptive. The persona 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 set Two new parameters were added to the “createmigration” command with host set and VVset.

Host set—a 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 set—a 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 6 illustrates the concept.

Figure 6. Host and Volume set

Technical white paper Page 13

Oracle RAC 11g migration HPE 3PAR OIU supports the migration of Oracle RAC and a single node database on host operating systems Red Hat® Enterprise Linux 6.3 or later if the Linux server is running native MPIO, the migration of the database can occur near online. The term “near online” refers to zoning changes yet to take place for migration and those changes may include some minimal disruption. HPE 3PAR recommends customers test these conditions prior to implementation. If the Linux server is using EMC PowerPath, then pre-migration steps included in the HPE 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 non-disruptive migration of Oracle 11gR2 RAC and single-instance databases using HPE 3PAR Online Import for EMC Storage Data Migration will not require the shutdown of the Oracle database host.

Prioritization of migration 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 total parallel moves which are active will be capped to 36, to prevent overloading the array. Mixing is recommended and will result in higher priority tasks finishing their migration sooner.

Migration of multiple source arrays As part of HPE 3PAR Storage Federation, HPE 3PAR OIU will support the ability to perform migrations from multiple host arrays to a single destination HPE 3PAR StoreServ Storage. Migration from each of the source to destination array is done sequentially. The following functionality is supported:

• Migration from multiple source to single HPE 3PAR StoreServ Storage (up to four sources supported)

• Source can be any of the supported arrays: EMC, HDS, IBM XIV (all supported versions)

• Unidirectional migration only

• Destination HPE 3PAR StoreServ Storage must be at HPE 3PAR OS 3.2.2 (IBM XIV requires MU2)

• 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

CLI scripting As part of the HPE 3PAR Online Import Utility for EMC Storage, the user can use scripting as part of an automation service to migrate data from EMC Storage to HPE 3PAR StoreServ Storage. Use the HPE 3PAR OIU CLI by executing the HPE 3PAR Peer Motion Utility shortcut. The scripting tool can be used in the following ways:

1. Execute only OIU CLI (as covered in this paper)

2. Execute OIU CLI with parameters

An example of an OIU CLI script is as follows; the script was titled “init.txt.”

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 OIU CLI. For a complete list of all HPE 3PAR OIU commands, refer to HPE 3PAR Online Import for EMC Storage Data Migration Guide. Commands are listed under the section “HPE 3PAR Online Import Utility for EMC Storage: Commands.”

Technical white paper Page 14

HPE 3PAR Online Utility installation and migration HPE 3PAR Online Import Utility installation The HPE 3PAR Online Import Utility is distributed as a free utility. Every new HPE 3PAR StoreServ Storage ships with a built-in 1 year license for the HPE 3PAR Online Import with the HPE 3PAR Operating System (OS) Suite. Users can gain access to the HPE 3PAR Online Import utility software through the HPE 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 HPE 3PAR Online Import Utility for EMC Storage can be installed on a physical or virtualized host. 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 7. The server software of the HPE 3PAR Online Import CLI Utility for EMC Storage is used to communicate with the EMC Solutions Enabler (SMI-S).

Figure 7. HPE 3PAR tool installation

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

• HPE Storage Migration Admins

• HPE Storage Migration Users

Technical white paper Page 15

Migration flow The Host Operating System of the migrated host dictates the path by which the user must perform migration tasks. Figure 8 contains the five steps for migration once all pre-work (SMI-S Provider, removal of EMC PowerPath, and zoning) is completed. The decision point after “createmigration” is whether the Host 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. The requirement for rebooting the array is referred as a “Minimally Disruptive Migration,” since the attached host is required to shutdown, zoning changes made, and migration started prior to the host being brought back online.

Some operating systems such as Linux do not need to reboot prior to the start of the migration process. The user is advised to follow process outlined in “HPE 3PAR Peer Motion and HPE 3PAR Online Import User Guide” for process used in the migration of data.5

Figure 8. HPE 3PAR migration flow and HPE 3PAR

Monitoring the migration During migration creation and migration of data, the user can monitor status of the preparation and migration process with the use of the command “showmigration.” Prior to a migration of data, the user must use the HPE 3PAR OIU commands to create the migration. During the migration creation a number of background processes occur such as, allocation of resources on the destination HPE 3PAR StoreServ Storage, copying of the source volume metadata which contains the attributes of the source volume and other background tasks associated with data migration pre-tasks. The user can monitor the preparation of create migration by issuing the command “showmigration” as illustrated in figure 9.

5 http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c04783896

Technical white paper Page 16

Figure 9. Migration creation

During the creation of migration, the migration ID is created. Once the migration creation is completed, a “startmigration” command is issued and the migration will commence. Monitoring the migration during the migration process is accomplished using the same “showmigration” command with the migration ID in the command line. An example of the output is illustrated in figure 10.

Figure 10. Monitoring migration

In the example illustrated in figure 10, a host set is being migrated. The illustration displays the progress of each of the volumes contained in the host set during the migration.

Using HPE 3PAR StoreServ Management Control System Reporter (2.3 and above) to monitor migration There is no direct report to display the migration; the user however can monitor the progress of the migration by monitoring the peer ports on the HPE 3PAR StoreServ Storage. Figure 11 is an example of creating a custom report, which monitors the peer ports. The report allows the user the ability to monitor the transfer rate graphically. The graph illustrated displays I/O size, service time, or latency of the transfer and the amount of IOPS. The illustration below represents monitoring the port at five-second intervals.

Figure 11. Monitoring migration using HPE 3PAR System Reporter

Technical white paper Page 17

Monitoring migration with HPE 3PAR CLI One final method to monitor the transfer rate in real time is by the use of the HPE 3PAR CLI. At the command line, the user would enter the command of statport –peer. The output of the command will show the transfer rate at near time ~1 second intervals. The display will continue to display until a key is pressed to stop the display. Figure 12 is an illustration of the statport command, the –peer identifies the port for display is the peer port.

Figure 12. CLI statport command

Migration performance During the process of migrating data from the EMC Storage array to HPE 3PAR StoreServ Storage, the paths to the EMC Storage array are removed as part of the process. During the migration process, the HPE 3PAR StoreServ Storage acts as a proxy array for all host data to the EMC array. Any file updates to the source storage volumes passes through the HPE 3PAR StoreServ Storage Peer Links and on to the EMC array.

Some minor latencies during the migration phase of the HPE 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 HPE 3PAR OIU 1.5 Performance enhancements were included in the current HPE 3PAR OIU 1.5. The enhancements have been 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 HPE 3PAR StoreServ Storage will be serviced by the local array instead of being serviced by the host array (EMC). This avoids the extra 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 EMC array when searching the hosts/LUNs.

Learn more at hpe.com/storage/3PAR

Technical white paper

Sign up for updates

© Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

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. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

4AA6-6485ENW, August 2016