Solved!
Go to Solutionlun migration.......................
LUN migration requirements
◆
The source and destination LUNs for the migration must reside in
the same storage system.
◆
You can launch only one LUN migration in a single operation.
◆
The source LUN cannot be a hot spare, or a binding, expanding,
migrating, or private LUN.
◆
The source LUN cannot be a component LUN of a metaLUN.
◆
The destination LUN must be the same size or larger than the
source LUN.
◆
The destination LUN cannot be a hot spare, a binding, expanding,
migrating, or private LUN.
◆
The destination LUN cannot be in a storage group.
◆
The destination LUN cannot be part of a SnapView, MirrorView,
or cloning operation
A migration can be in any of the following states:
◆
Queued
◆
Migrating
◆
Faulted
◆
Migrated
◆
Transitioning
To migrate a LUN:
1. Ensure that the source and destination LUNs meet the
requirements described earlier.
2. In the
Storage tree, navigate to the LUN or metaLUN whose data
you want to migrate (source LUN).
3. Right-click the LUN or metaLUN and click
LUN Migration >
Migrate
ASAP, High, Medium, or Low.
6. If the LUN choices and migration rate you specified are correct,
click
OK.
Manager displays a confirmation box, and, if the destination LUN
is larger than the source LUN, a warning. The warning states that
you are changing the LUN size and should verify that all attached
hosts can handle such a dynamic change.
7. To continue with the migration, select
Yes.
The LUN migration starts.
Also, there is very good information in the on-line Help and on POwerLink:
White Paper: EMC Virtual LUN Technology - A Detailed Review
http://www.emc.com/collateral/hardware/white-papers/h1529-emc-virtual-lun-tech-wp-ldv.pdf
glen
RRR
6 Operator
•
5739 Posts
1007
0
Posted January 25th, 2010 23:00
Create an equally large LUN on another RG; the LUN number doesn't matter. Right click on the LUN you want to be moved and choose migrate. Then select the LUN you just created. The LUN will be moved on the fly, transparrent to the user, so you don't notice anything and don't need to change anything afterwards. You might want to consider setting the priority, since on heavily used LUN's, you might notice a performance degradation. After the migration is done the temporary LUN will be gone.