EVA HP Storage Thin

HP EVA to HP 3PAR Online Import

What is it?

Now this is really cool, at a high level these new announcements now give you the risk free incentive to move your current workloads residing on an HP EVA P6000 to HP 3PAR and benefit from a leading storage platform.


HP EVA to HP 3PAR Import

So if you are currently running an existing HP EVA box and love the new HP 3PAR platform. I introduce to Online Import!


Online Import migrates volumes from a HP P6000 EVA to an HP 3PAR StoreServ system

Volumes are migrated online, minimally disruptive or offline depending on host OS, and best of all you can migrate full to thin volumes (and back again)


Online Import from EVA to 3PAR directly from EVA Command View:















Seamlessly move from your legacy HP EVA array to the new 3PAR architecture, and reek the benefits that it has to offer virtual environments including:


Thin Conversion

Go thin on the fly! The migration will be performed enabling the reclamation of 128MB regions using the hardware based Gen4 ASIC magic, allowing in-line, wire-speed “fat-to-thin” conversions compatible with any host volume.

Zero Detection.

Stay thin! As data is written to new 3PAR LUN, provided you have zero detect on your existing thick LUNs will shed the weight and become thin!

Note: There are still some operating systems that do not support the automatic reclamation of space using the T10 UNMAP command. Have a read on my VMware-related post on this notion here.

Storage Tiering – LUN and Sub-LUN (Block)

Automatic data-driven and policy-driven response to data placement. Simply put – busy workloads reside on faster disk to service the IO queue, and less busy reside on cheaper disk. Just simple!


There is a 180 day time based Peer motion shipped free, this license time starts at installation time, so if the license is enabled at the factory then it will start to tick down.

The license will generate appropriate alerts once the 180 days is drawing close.

Alternatively there is a permanent license too!


What is the difference between the existing Peer Motion and Online Import

The fundamental difference between these two offerings is based on the source array:

  • Peer Motion deals with HP 3PAR to HP 3PAR arrays only whereas
  • Online import deals with HP EVA to HP 3PAR arrays.


The other difference that one is disruptive (associated outage for cutover) and one is non-disruptive.  I still recommend VMware Storage vMotion over disruptive methods if time is not an issue for obvious reasons.


Supportability – EVA to 3PAR Import roadmap


So what’s the catch?

Of course with any migration, there are pre-requisites and requirements some are obvious and some are not.  The main pre-requisites are

  • Current version of OI supports only EVA x400 series running min firmware XCS09534000 to EOS/P7000


  • Destination array: HP 3PAR StoreServ 7000 or 10000 running HP 3PAR OS 3.1.2 (not 3.1.1!!)


  • So there is no Online Import license for F- and T-Class, meaning F- and T-Class cannot be target for Online Migration …. However we can use the Peer Motion license for F and T (associated costs).


  • vDisks that are larger than 16TB cannot be migrated (unsupported size on 3PAR presently)
  • All vDisks presented to a host are migrated (no subset selection possible…..yet)


  • No support for HPUX hosts and\or clusters


  • Does not support Linux or Solaris clusters (Windows and VMware ESXi clusters only)


  • Can only migrate one HP EVA and one host at a time


  • Access to a box with HP P6000 Command View 10.2 to facilitate the migration which also has FC connectivity to source P6000 EVA and has IP connectivity to destination HP 3PAR StoreServ system over TCP ports 5781 (3PAR Events) and 5783 (3PAR Secure CLI).


How do I get it?

Easy! Online Import is part of the “Typical” Install Set for HP P6000 Command View 10.2

3RD party array -> HP 3PAR

So what happens if you are running a 3rd Party Array and wish to transition to HP 3PAR?  No problem, get in touch with our storage consulting team who has a vast amount of experience in this solution.

Have a read of my HP MPX200 post to gain an insight on the method we use, fast, risk-free and best of all giving you the ability to go thin on conversion.


Need a hand? Sure! Try our Storage Consulting Migration Services.

Get in touch, we have start-up services and care packs to make the ordering part simple!


HP EVA to HP 3PAR StoreServ Acceleration Service

That’s its folks, Some REALLY cool stuff has just been announced, Move to an awesome new storage platform and use a risk-free way to transition from your current EVA to it.

My colleague Francis Scarfi did a good write up on this service


Follow me on twitter @andrecarpenter


7 Comment

  1. Andre,
    Unfortunately at least one big piece of that matrix is wrong, ESXi 4,5 online migrations are NOT supported. I just got an update from HP stating as such. This is a bummer for us as we have an pRDM that this would have been nice to use to move, looks like it’s robocopy to the rescue again.

  2. Hi Andrew,

    Correct – I wrote this post before this changed. 🙁 – I’m not sure of your circumstances, but we state it is not supported (but not necessarily enforced) so you should be able to still migrate it using Online Import. Perhaps create a dummy RDM to a non-prod VM and try it out.

    If that isnt possible then we are recommending storage v-Motion for VMFS over Online Import until this is supported and for RDM’s – Will need to be guest based tools (Like good old Robocopy) to migrate.

    Also, I think Cormac Hogan from VMware wrote a few posts (http://blogs.vmware.com/vsphere/2012/02/migrating-rdms-and-a-question-for-rdm-users.html) on converting RDM’s to VMDKs, I’ve not tried it myself but could be worth a read.

    Let me know!

  3. @andre
    Unfortunately the reason we’re using a pRDM is that we have a volume that is larger than 2TB and so we can’t use any other method. Since this is the largest share in our org and used by every department there’s no way we’d use an unsuported method so we’ll just robocopy it. At the end of the day it’s a much smaller deal than moving all the volumes on the physical database servers which the online migration tool does support but it was a little bit of an aw shucks moment.

  4. Hi Andre,

    “No support for HPUX hosts and\or clusters ” , is update?

    7 HP-UNIX hosts shared EVA6400, plans to use 3par ss7200 alternative EVA6400, whether to use an online migration ?


This site uses Akismet to reduce spam. Learn how your comment data is processed.