You can migrate the LUN as the other already mentioned and play around with the speed settings. High migrates at around 10GB per hour and I've seen ASAP do a wonderful 120 MB per second (40 times faster than "high"). The ASAP setting will have an impact on performance though, so be careful. You can change it during the migration.
how does the LUN migration functionality affect an ESX environment? I would assume ESX servers would have to see the new LUN. How does this affect running virtual machines as well?
There is no new LUN ! The "old" LUN is migrated to a new location but stays the same LUN with the same HLU and everything !!! The host doesn't see any difference !
Including the extra space if you migrate to a larger LUN - each host OS needs to do something to see the extra space - this is not automatic at the host level.
we have just done this for a customer in a ESX production environment.
1: connected to extra trays with 30 disks. 2: migrated production luns to new raidgroups 2: redesigned original raidgroup layout 3: migrated luns back 4: took temp. trays with me again.
I am using a CX3-20 Clariion and i am running into the same issue. Any idea what the speed would be going from FC to SATA? I have read the White Paper on The Influence of Priorities on CLARiiON LUN Management Operations - Applied Technology it gives examples but not from SATA to FC or vice versa.
I think you have 3 ways to do it. 1.Create metalun, in this case you create a second lun in RGB, and with right clicking on first lun choose expand. In this case you can create a concatenate or stripe lun. Concatenate method add extra space to lun immediately and not depend on forst lun size. Striping require a second lun with the same size and need more time to build it, but performance is grow up. After that you need resize lun. 2.Create a new lun and migrate first lun, how described early. 3.If i remember properly, you can add extra space to ESX just adding new lun to esx server.
snadora
2 Intern
•
49 Posts
0
June 3rd, 2008 12:00
RIght click on existing LUN and click on migrate option on Navisphre GUI.
dynamox
9 Legend
•
20.4K Posts
0
June 3rd, 2008 12:00
RRR
4 Operator
•
5.7K Posts
0
June 4th, 2008 01:00
odurasler
1 Rookie
•
103 Posts
0
June 11th, 2008 19:00
RRR
4 Operator
•
5.7K Posts
0
June 12th, 2008 03:00
kelleg
4 Operator
•
4.5K Posts
0
June 12th, 2008 12:00
regards,
glen kelley
odurasler
1 Rookie
•
103 Posts
0
June 12th, 2008 18:00
it seems i need to test this theory.
dynamox
9 Legend
•
20.4K Posts
0
June 12th, 2008 19:00
it seems i need to test this theory.
it's a proven working functionality that has been available since flare 16 or 19 i think
jgrinwis
1 Rookie
•
99 Posts
0
June 20th, 2008 08:00
1: connected to extra trays with 30 disks.
2: migrated production luns to new raidgroups
2: redesigned original raidgroup layout
3: migrated luns back
4: took temp. trays with me again.
RRR
4 Operator
•
5.7K Posts
0
June 22nd, 2008 01:00
jgrinwis
1 Rookie
•
99 Posts
0
June 23rd, 2008 06:00
RRR
4 Operator
•
5.7K Posts
0
June 24th, 2008 01:00
Hubble1
12 Posts
0
July 11th, 2008 09:00
Thanks
undertaker98
75 Posts
0
July 14th, 2008 01:00
1.Create metalun, in this case you create a second lun in RGB, and with right clicking on first lun choose expand. In this case you can create a concatenate or stripe lun.
Concatenate method add extra space to lun immediately and not depend on forst lun size.
Striping require a second lun with the same size and need more time to build it, but performance is grow up.
After that you need resize lun.
2.Create a new lun and migrate first lun, how described early.
3.If i remember properly, you can add extra space to ESX just adding new lun to esx server.