Recently I did a VMware migration from an EMC VNX array to a
new HP 3PAR array. When migrating VM’s the obvious tool to use is Storage
vMotion. This allows an online, non-disruptive, and fast migration process. The
process is easy to use and easy to setup. Here is a high level guide detailing
the process for a fiber channel SAN fabric. Enjoy after the jump.
1.
Verify all zoning to VMware Host Cluster
a.
Create zones between all ESXi host HBAs and the
designated 3PAR front end ports.
b.
Make sure to follow 3PAR best practices for
zoning to VMware.
c.
Create the hosts on the 3PAR array.
i. Pick
persona 11 (VMware host persona).
ii. Add
correct WWN’s to each host.
iii. Optionally
you can add all the hosts to a Host Set for easy LUN Masking.
2.
Create Virtual Volumes on the 3PAR array.
a.
Create Virtual Volumes of the desired size.
b.
Typically 2-4 TB’s are recommended for standard
shared VMware Datastores.
3.
Export Virtual Volumes to VMware host set to
complete LUN Masking.
a.
You can also export Virtual Volumes to each
individual host if desired.
4.
Rescan all hosts inside VMware.
a.
Paths should now be seen to 3PAR array.
5.
Create VMFS Partition/Datastore for each exported
3PAR VLUN.
a.
Recommend using naming convention that includes
Host LUN ID in name for easy matching to associated Virtual Volume on 3PAR.
6.
Add SCSI claim rule to VMWare ESXi hosts to set
Round Robin pathing to all newly added 3PAR Datastores.
a.
Round Robin is the required Multipathing for
VMware and 3PAR arrays.
b.
A VMware SCSI claim rule will allow the ESXi
hosts to assign Round Robin Multipathing by default to newly created datastores
exported from the 3PAR array.
i. Reboot
of each host will be required after the setting is applied.
7.
Migrate a single VM to newly created 3PAR
Datastores.
a.
This allows for testing and confirmation of
above operations.
8.
Migrate remaining VMs from exiting VNX
Datastores to new 3PAR Datastores.
9. Pat yourself on the back for moving to a class
leading storage array.