EMC VNX LUN Migration Proven Best Practises.

LUN Migration moves data from a source LUN to a destination LUN (of the same or larger
size) within a single storage system. This migration is accomplished without disruption to the
applications running on the host. LUNs can be the target or source of LUN migration
operations. LUN Migration can enhance performance or increase disk utilization for your
changing business needs and applications by allowing the user to change LUN type and
characteristics, such as RAID type or size, while their production volume remains online.
LUNs can be moved between pools or to a traditional LUN in another RAID group. When
migrating a thin LUN to another thin LUN, only the consumed space is copied. When
migrating a thick Pool LUN or traditional LUN to a thin LUN, the space reclamation feature
is invoked and only the consumed capacity is copied.

LUN migration allows data to be moved from one LUN to another, regardless of RAID type,
disk type, LUN type, speed and number of disks in the RAID group or Storage Pool with
some restrictions. The process involved in the migration is the same across all VNX systems.
On VNX series with the Thin provisioning enabler installed, LUNs can be migrated from a
Thin

or Thick LUN to a traditional LUN and vise-versa.

The LUNs used for migration may not be private LUNs or Hot Spares, nor may they be in the
process of binding, expanding or migrating. Either LUN, or both LUNs, may be metaLUNs.
Neither LUN may be a component LUN of a metaLUN. The destination LUN may not be
part of SnapView Snapshot, SnapView Clone or MirrorView operation. This includes Clone
Private LUNs, Write Intent Log LUNs, and Reserved LUN Pool LUNs.
Note the Destination LUN is required to be at least as large as the Source LUN, but may be
larger.

The LUN Migration feature is transparent to any host accessing the Source LUN, though
there may be a performance impact. Copying of data proceeds while the Source LUN is
available for read/write access, and the copy process may be terminated at any time. Once all
data is copied, the Destination LUN assumes the full identity of the Source LUN, and the
Source LUN is unbound as a security measure. The host accessing the Source LUN sees no
identity change, though of course the LUN size
may have changed. In that case, a host utility, such as Microsoft Windows diskpart, can be
used to make the increased space available to the host OS.