3PAR StoreServ Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

SOLVED
Go to solution

Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Hi guys.

I have real pending migration from HP EVA 4400  to  new HPE 3PAR 8200

The  mission objective :

To migrate all data from HP EVA 4400 to NEW  HPE 3PAR 8200

Current Infrastructure :

C7000 Blade Enclosure

5 x BL460c Blade Servers

2 x SAN SW

HP EVA 4400

MS Failover Cluster  2012 R2

All  5 x Blade SRV`s are booting from the EVA LUN`s  and this is my top concern.

What is the Best approuch  to migrate boot LUN`s  from EVA to 3PAR ?

As for the rest of the Production data  -  i think  i`ll skip HP On-line Import and i`ll bet on  MS Datastore On-line migration !

Any advice from some one allready done this  in real action plan  is highly appreciated.

 

Kind Regards

Nik

 

 

 

 

Niksavoy
5 REPLIES
giladzzz
Honored Contributor

Re: Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Hi

Best way I found to migrate boot disks is to shutdown the server do a snapshot of the boot disk

and do an offline migration of the snapshot than change the boot settings of the server from EVA to

3PAR. the copy of the disk to 3PAr is fast as it is usually a small disk.

as for the rest you can do a minimally distrupive migration or use other method

all work fine.

Regards

 

Re: Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Hi  giladzzz  and  thank You for the Replay.

Can You be more specific  in details :

do a snapshot of the boot disk   -  like from CV  ?

offline migration of the snapshot - with HP EVA Online Import tool ?

 

Kind Regards  Nik.

Niksavoy
giladzzz
Honored Contributor

Re: Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Hi

the answer to both your questions is yes

if you take a snapshot it means you keep your original boot disk.

remember eva to 3par migration keeps the disk wwn from the source

(that is the eva) sometimes its good to change it to 3PAR wwn

you can do it in 3PAR CLI ""setvv –wwn auto <vvname>""

this is an offline process.

Regards

Give a KUDO if this helps

Re: Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Thank You for the advise !

After the migration i`ll give  kudos or i`ll share my  migration action   plan :)

 

Kind  regards

Niksavoy
Solution

Re: Best approuch for migrating Boot-LUNS for Blade Servers from EVA4400 to 3PAR 8200

Hi Guys.

And the Kudos  goes to :

EaseUS Partition Master Server

I managed to  make full Disk Clone  from  old EVA 4400 Boot LUN  to NEW  3PAR  Boot LUN  under Windows 2012 R2  OS  Environment using EaseUS Partition Master Server 

After  compleating the  disk clone  i have  changed the  Boot LUN  from FC Adapter from the OLD  EVA  to  NEW 3PAR  and  VOALA  :)

Job DONE   :)

So   having  24/7   Hyper-V  Failover Cluster with 4TB  data  and   FULL Datastore Live-Migration  from EVA 4400   to 3PAR 8200   took me  about 2 h 30 min.

And the BEST OF ALL    ZERO  DOWN TIME  !

P.S. -  giladzzz  Kudos for You also - for the sigjestions  after all it is eventually a possible plan

Niksavoy