This post is more than 5 years old
2 Intern
•
43 Posts
2
4568
September 29th, 2010 03:00
Clariion LUN migration
Can you please tell me the step by step procedure for LUN migration
1. Precautions to take or precheck list before go for LUN migration.
2. precautions to take while LUN migration process.
3. Post check list for after LUN migration.
No Events found!


kenn2347
4 Apprentice
•
542 Posts
0
September 30th, 2010 07:00
Well migrating luns on the same array is easy.
1 Create new lun of equal or bigger size
2 Right click source lun and select "Migrate" Select new lun
3 Set a migration speed. This uses Storage processor CPU so if your systems are using hi I/O, better to start at a lower speed. It just might take along time.
4 When it finishes, the new lun assumes the disk signature of the old one so you don't have to do nothing on the host unless you migrated to a bigger lun. If so, you will have to use diskpart (windows) to extend the lun so the OS see's all the space.
As for migrating to other arrays, there are so many products out there that i dont have the time to explain each one. Some of them are SanCopy, Mirrorview, Open Migrator, PowerPath Migration Enabler. I am sure there are more i cant think of.
I can see that you recently posted a bunch of questions and it sounds like you might be sort of new to EMC array's? If that is the case, at the top of the Clariion forums is a tab for "Documents". There is a lot of good information in those documents and they can answer pretty much all the questions you asked. I would recommend that you read some of them and if you still have questions, then come back and ask.
This commutiy is very responsive and always willing to assist other members:)
Thanks
kenn2347
4 Apprentice
•
542 Posts
0
September 29th, 2010 06:00
It depends on what type of migration you are asking about. are you asking about a Array based migration(Where luns are moved around within the same array) or migrating from one array to another?
lakshman1
2 Intern
•
43 Posts
0
September 30th, 2010 00:00
Both, migrating luns with in the array and migrating the luns to remote array.
kelleg
6 Operator
•
4.5K Posts
0
September 30th, 2010 12:00
I've attached an older document about LUN Migration when it first came out - can't find a new document and most of this information is now in the Help.
glen
1 Attachment
EMC LUN Migration.pdf
stadivaka
38 Posts
0
January 10th, 2011 11:00
Hi,
We are facing some performance issues on one of the Raidgroup, EMC suggested us to migrate the current meta Lun 804. Clarriion model is CX-380 with FLARE 22 [03.22.080.5.508]
This Lun is using on 5 ESX hosts inturn assigning by VMGuests. I would like to know if we plan for Lun migration does these ESX/VmGuests will be impacted ?
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
January 10th, 2011 11:00
LUN Migration when set to Medium priority should not be host impacted, i prefer to do host migrations during low I/O periods.
NetSupport
5 Posts
0
January 10th, 2011 12:00
Best to do lun migrations with priority of High or less in order to reduce possibility of contention or cache issues. ASAP should only be used in very specific circumstances. After hours (off-business) always best. Keep in mind the lower the priority the longer it will take to migrate but less chance of impact.
Storagesavvy
474 Posts
0
January 10th, 2011 13:00
LUN Migration keeps host ID, LUN WWN, etc the same so the host will not notice the change. In fact, sometimes you will notice that a migration from RAID5 to RAID10 or similar, the LUN will still show the old RAID type when queried by the host.
Richard Anderson, EMCISA
Sr Technology Consultant, Western Division, EMC
richardj.anderson@emc.com - 206.229.9263
about.me/richardanderson
stadivaka
38 Posts
0
January 10th, 2011 13:00
Okay sure, after the Lun migration Meta Lun 804 [host id is 1] to Meta Lun 113 for example, the host id will be same right.
stadivaka
38 Posts
0
January 10th, 2011 14:00
Okay thanks Richard.
SKT2
2 Intern
•
1.3K Posts
0
January 20th, 2011 03:00
The adavantage with LUN migrator is the new one take the identify of the old LUN. But the old LUN would be dsetroyed at the end of the operation. with Other host based migrations we ma have an option of preserving the old data for some more time.
DanJost
190 Posts
0
January 20th, 2011 06:00
My 2cents added to Kenn2347's comments...
When creating the destination LUN, create it using blocks instead of GBs or MBs. You can get the exact number from the original LUN properties. This will ensure that the LUN is exactly the same size.
Dan