VNX: Requirements for LUN Migration in VNX array (User Correctable)

Requirements for LUN Migration in VNX array.

LUN migration is supported on all LUN types, In order to migrate all the data of a source LUN to the destination LUN , Customer must need to follow the below requirements.

1) The source and destination LUNs for the migration must be in the same storage system. 
2) Customer can launch only one LUN migration in a single operation. 
3)The source LUN cannot be a hot spare, or a binding, expanding, migrating, or private LUN. 
4) The source LUN cannot be a component LUN of a metaLUN
5) The destination LUN must be the same size or larger than the source LUN. 
6) The destination LUN cannot be a hot spare, a binding, expanding, migrating, or private LUN. 
7) The destination LUN cannot be in a Storage Group. 
8) The destination LUN cannot be part of a SnapView, MirrorView, or cloning operation.

LUN can be migrate in the same pool ,or in the different pool of the array.

Most common questions asked on LUN migration:

1) Is LUN Migration an online activity wherein a LUN can still be used while the migration is in progress?

Answer:: Yes , it is an online activity ,during the migration the source LUN remains online during the entire migration process so that the host application can continue sending I/O traffic to the source LUN without interruption. Once the user starts the migration, the migration process begins and the selected target LUN eventually becomes the source LUN with "all" characteristics of the original source LUN.

2) What will happen to the data on the source LUN after migration? Will it be gone? 

Answer: The source LUN will be unbound , all the data will be copied to the destination LUN.

3) After Lun migration would the newly created lun be connected automatically on the same host which the Source Lun was attached? 

Answer: Since LUN migration is invisible to a host, no changes will be required to be made to the Cluster. LUN migration preserves the host-visible aspects of the source LUN so the destination LUN will appear to the host the same as the source LUN did before the migration (that is, have the same WWN number). 

4) Would there be any impact to the host during migration? 

Answer: No impact to the host , the database or any host application using that LUN does not have to be shut down during its migration.
1) Is LUN Migration an online activity wherein a LUN can still be used while the migration is in progress?