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:)
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?
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.
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 ?
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.
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.
kenn2347
4 Apprentice
•
542 Posts
1216
0
Posted 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