This following steps are for migrating a Windows 2008 R2 box
from an EMC VNX to HP 3PAR. The tool offers migration for Oracle (RAC
included), Windows (clusters included), Linux, and Hyper-V. You also have 3
migrations types: online, minimally disruptive migration (MDM), and offline. I
will be using the minimally disruptive migration (MDM). Please review the
official HP documentation before attempting as I will not be covering every
single pre and post item in this guide.
Build/select a machine to install the 3PAR
Online Import Utility.
Must be Windows based machine.
EMC SMI-S Provider (Solutions Enabler).
Install version 220.127.116.11
Use Default destination folder for install
Select Array Provider under the Provider List.
Leave defaults for daemon list.
Configure EMC SMI-S Provider
Open a Windows command prompt on the server
where the EMC SMI-S Provider software was installed.
Change the directory to the location of the EMC
SMI-S Provider installation. The default is: C:\Program Files\EMC\ECIM\ECOM\bin
Start the testsmiprovider program.
Accept all default settings when prompted.
Attach the VNX storage system to the EMC SMI-S
the addsys command.
#1 for Clar (Array Type)
in IP address for SPA then SPB.
You don’t need anything for array id 2 as you
only have 2 SP IP’s.
Address types pick default of 2.
in user name and password
This needs to be an EMC VNX global administrator
the Output reads as 0 you have established communication.
can also run the dv command to verify the communication to the VNX.
If SMI-S has client IP filtering enabled you
will need to add the 3PAR Online Import Utility servers IP to the trust listed.
Please refer to the HP documentation for further
Install 3PAR Online Import Utility.
Install the 1.3.0 version of the online utility.
Choose the default settings.
the client and server for install.
This guide covers the online utility install on
a single server. Refer to the HP documentation if you wish to split up the
guide does not cover the CA certificate section of the installer. If you
require this please refer to the HP documentation for further instructions.
Configure 3PAR Online Import Utility.
Once installation is complete you will need to
add an account with local machine administrative privileges as a member of the HP
Storage Migration Admins group.
group was created, on the local machine, during the installation process.
account added here will be used to run the migration utility.
will also see an HP Storage Migration Users group. This group will not be
needed for the purposes of this guide.
Launch the tool.
can use LOCALHOST for the IP address if the client and server portions were
installed on the same machine (both were installed on same machine for this
in credentials from the account above added into the local group the HP Storage
Migration types and pre-planning.
Please refer to the HP documentation for migration
types and pre-planning steps.
This guide will use minimally disruptive
migration (MDM for the migration type).
Two unique paths (only 2 paths) must be zoned
between the source and destination storage systems. To create two paths, two
controller ports on the source EMC Storage system must be connected to two peer
ports on the destination HP 3PAR StoreServ Storage system.
The peer ports on the destination HP 3PAR
StoreServ Storage system must be on adjacent nodes: 0/1, 2/3, 4/5, or 6/7.
Zone the source and destination systems together
and make sure they are visible to each other before zoning hosts to the
Do not unzone the source and destination systems
from each other until the data migration is complete.
On the destination HP 3PAR StoreServ Storage
system, configure two free ports as peer ports using adjacent nodes: 0/1, 2/3,
4/5, or 6/7.
the port connection type to point.
the port connection mode to peer.
WWN of a host port changes when it is set to become a peer port. Use the new
WWN of the peer port in the zoning.
Create two zones between the source EMC Storage
system and the destination HP 3PAR StoreServ Storage system, ensuring that one
EMC host port is in the same zone with one HP 3PAR peer port.
Each zone should contain only two ports: one
from each storage system. Adjacent HP 3PAR peer nodes should be zoned to
separate EMC controllers in a one-to-one mapping. For example, zone the peer
port on node 0 on the HP 3PAR StoreServ Storage system to controller A on the
EMC Storage system, and zone the peer port on node 1 on the HP 3PAR StoreServ
Storage system to controller B on the EMC Storage system.
Verify that the EMC Storage system is shown as a
connected device on both peer ports of the destination HP 3PAR StoreServ
check peer port connections from the HP 3PAR StoreServ Storage, issue the
showtarget command with the -rescan option, and then issue the showtarget
Add the Source Storage System
From the HP 3PAR Online Import Utility, issue
the addsource command.
-type VNX -mgmtip XX.XX.XX.XX -user admin -password adminpw —uid
XX.XX.XX.XX is the IP address of the EMC SMI-S
xxxxxxxxxxxxxxxx is the WWN of the EMC Storage
–user and –password is the account used on the
EMC SMI-S provider.
Issue the showsource command to verify the
source storage system information.
Add the Destination Storage System
From the HP 3PAR Online Import Utility, issue
the adddestination command.
–mgmtip XX.XX.XX.XX –user 3paradm –password 2Password
XX.XX.XX.XX is the HP 3PAR management port IP
Use a 3PAR super user account for –user and
If a certificate validation error occurs on the
adddestination command, first run the installcertificate command, then run the
adddestination command again.
Issue the showdestination command to verify the
destination storage system information.
Preparing the Host for Data Migration
Stop all applications on the host that may be
accessing the LUNs to be migrated. This also includes any replication and
backup applications on the LUNs.
Set the LUNs to be migrated to an
Modify the startup scripts for all applications
and services that are using the migrating LUNs to prevent them from starting at
the next reboot. They should remain disabled until after the migration has
started and documentation instructs you to bring your host back online.
Creating the Data Migration Task
Host and volumes must be in supported storage
group configuration on the source EMC Storage system.
On a VNX source storage system, two HP 3PAR
initiators are added to the storage group that contains the hosts or volumes
being migrated. The host name of the HP 3PAR initiators is unknown. The
initiator name appears as the WWN of the peer port on the HP 3PAR StoreServ
For MDM migration, the host or hosts that are
being migrated are created on the destination storage system. A host set is
also created on the destination storage system.
The createmigration command performs the
following checks before creating the migration:
migration task for the specified source storage system exists. Only one
migration at a time can be provisioned for a given source EMC Storage system.
source storage system group configuration is valid.
The volumes or hosts specified in the
createmigration command are mapped to a storage group on the associated source
EMC Storage system. All LUNs and all hosts in the mapped storage group will be
migrated even if only a subset are entered in the createmigration command.
SMI-S Provider version.
storage system model number.
Protocol must be Fibre Channel.
A LUN under replication cannot be migrated.
Using the HP 3PAR Online Import Utility, issue
the createmigration command with the -migtype MDM option.
-sourceuid 50067890C6E059EE -srchost "HPDL585-01" -destcpg FC_r5
-destprov thin –migtype MDM —persona “WINDOWS_2008_R2”
For supported persona types and syntax please
refer to HP documentation.
Make a note of the migration ID, as it will be
used in commands to track migration progress.
the showmigration command to verify that the data migration task preparation
has completed successfully.
may take some time. Upon successful creation of the createmigration task, the
STATUS column in the showmigration command output will indicate
preparationcomplete(100%). When this status is indicated, continue to the next
Updating Host Multipath Software and Unzoning
from the Source EMC Storage System
2008 R2 requires Windows native MPIO to manage the paths.
PowerPath must not be installed during the migration process.
all applications before removing EMC PowerPath.
you are uninstalling EMC PowerPath from a Windows host where the host is
booting over SAN from the source system, you will be prompted to restart before
removal is completed. This restart is required and must be completed.
removal, you will be prompted to restart the host in order for the changes to
take effect. Do not restart at this point.
removal of EMC PowerPath Multipath software may have also disabled the MPIO
installation without removing it. Manually check to see whether the native
Microsoft MPIO is still loaded, and if it is, fully remove it at this time. Now
restart the host.
the host to the destination HP 3PAR StoreServ Storage system to establish
the HP 3PAR Management Console, verify that the host whose LUNs are under
migration has paths to as many HP 3PAR controller nodes as are zoned in the
MPIO multipath software on the host.
the Windows native multipath MPIO (if it is not already not enabled).
HP 3PAR LUN types with MPIO by configuring MPIO to use 3PARdataVV (case
sensitive) as the device hardware ID.
will be prompted to reboot the host in order for the change to take effect. Do
not reboot at this point, since the MDM procedure will require stopping the
down the Windows host. Leave the host offline until the migration is started.
the source EMC Storage system from the host.
Starting the Data Migration from Source EMC
Storage System to Destination HP 3PAR StoreServ Storage System
the HP 3PAR Online Import Utility, issue the startmigration command.
-migrationid (in the example above, 1411673030253) will have been assigned by
the createmigration command.
view the status of the migration, issue the showmigration command.
the showmigrationdetails command to verify the volumes being migrated.
the preparation stage, PROGRESS for each volume will be 0% and the TASK_ID will
task ID will be assigned and percentage of progress will be shown while the
task is being executed.
STATUS column in the showmigration command output will indicate success when
all volumes have been migrated successfully.
Bringing the Windows Host Back Online
that the import has started and confirm that a TASK_ID is available for each
volume by issuing the showmigrationdetails command.
is unsafe to bring the hosts back online if the TASK_ID number is not yet
available in the output of showmigrationdetails.
the import has started for the volumes, bring the Windows host that was shut
down back online.
a Windows host that is booting over SAN from the source system, the HBA BIOS
must be reconfigured during host startup to select the HP 3PAR boot device. If
this is not done, the host will not start up.
the disk status by pointing to diskpart.exe or by opening Disk Manager.
on the Windows SAN Policy, the disks that were migrated are offline or online.
If offline, use diskpart or the disk manager to bring them online.
can now restart the host and restart all applications and services. The host
may resume normal operations.