When you create a MetaLUN, the original LUN and the additional LUNs are combined to form a MetaLUN. Now depending on several factors, these LUNs will either be grouped as 1 component or multiple components under the MetaLUN. Either way, the individual LUNs that make up the MetaLUN are marked Private once the MetaLUN is formed. According to EMC LUN Migration (Virtual LUN) documentation, a Private LUN is not eligible for migration. It goes on to mention that Component LUNs of a MetaLUN are not eligible either.
I was hoping I could just migrate (move) a single component of a Meta LUN from one RAID Group to another without having to migrate the entire LUN. This would be useful if you wanted to reconfigure a RAID Group and needed to move LUNs off it.
In my case, I have a RAID Group that I'd like to remove a disk from but need to clear the LUNs off it 1st and I'd rather not migrate entire Meta LUNs that just have one component on this RAID Group.
I am pretty sure this is impossible. According to CLARiiON Host Integration and management Student Guide. When a metaLUN is destroyed, all LUNs involved with its components, including the Base LUN, are unbound, and all the data on the all the LUNs is lost.
Your best bet is to present another LUN to the host and just copy the data off and then destroy the metaLUN.
or if you have space in another raid group ..create another LUN and migrate data to it using NaviSphere migrate functionality, it's done online and the host would never know.
The Navisphere Manager Migrate is the feature I am using. But my question is, can the migrate feature be used to migrate a single component of a Meta LUN from one RAID Group to another?
We might need clarification. Are you trying to migrate Data or are you trying to migrate disks out of the MetaLUN. I'm not exactly sure what you mean when you use the phrase "Single Component".
I am wanting to migrate (move) an individual private LUN that is one of the components of a striped Meta LUN. For example, I want to move LUN 22 [4001; RAID 5] from RAID Group 1 to RAID Group 5. The goal is to get everything off RAID Group 1 so I can destroy it and re-create it with less disks. And, I don't want to have to migrate entire Meta LUNs which affect four other RAID Groups.
You know, it's easier to add than to take away! It appears I will have to migrate (move) all of the Meta LUNs that touch this RAID Group (and touch four other RAID Groups) and then I can destroy this RAID Group, recreate it, and move everything back. What a pain!
Unfortunately, I believe you are correct. The fact they're private and not eligible for migration is the killer. Unless EMC has a secret "back-door" way to do it.
Collier2
8 Posts
482
0
Posted August 2nd, 2007 07:00
When you create a MetaLUN, the original LUN and the additional LUNs are combined to form a MetaLUN. Now depending on several factors, these LUNs will either be grouped as 1 component or multiple components under the MetaLUN. Either way, the individual LUNs that make up the MetaLUN are marked Private once the MetaLUN is formed. According to EMC LUN Migration (Virtual LUN) documentation, a Private LUN is not eligible for migration. It goes on to mention that Component LUNs of a MetaLUN are not eligible either.