We currently have all our reserved lun pool luns on SATAII drives and we¿d like to migrate all of them to FC drives, what would be the way to do this? Thanks
Create new ones on FC and replace the SATA ones with FC ones. Don't do them all at once (you can't when they're in use).
So after you created new ones on FC, take out 1 unused SATA LUN and put in a new one. Do this for all SATA RLP LUN's. You will run into SATA LUN's that are in use.... at a given point in time you'll need to shut down MV for a minute or so, but I think you'll manage to replace them all by hand.
those are private LUNs so i don't' think you can migrate them using Lun migration utility. Are they actually in use ? What are they used for snapview or sancopy ?
Sounds like a plan, thanks... When you say "shut down MV for a minute or so..." I should use AdminFracture for this step, correct?
If I AdminFracture the MV/A luns, I shouldn¿t have to perform the full synch for those luns once the replication restarts, correct?
Create new ones on FC and replace the SATA ones with FC ones. Don't do them all at once (you can't when they're in use).
So after you created new ones on FC, take out 1 unused SATA LUN and put in a new one. Do this for all SATA RLP LUN's. You will run into SATA LUN's that are in use.... at a given point in time you'll need to shut down MV for a minute or so, but I think you'll manage to replace them all by hand.
You don't need the LUN migration utility. If they're not in use, you can pull them out of the RLP at any time, just make sure you replace them with new ones asap just incase the Clariion needs them.
If possible yes. Most customers know have the maximum amount of LUN in the RLP, so adding just 1 isn't even possible before you take 1 out first. But you're right !
To be safe I would just add the new FC RLP LUNs in first. That way when you remove the STATA LUNs from the pool you are not at risk of not having enough RLP storage available.
Reserve LUNs (RLP) are used by Mirrorview/A - one for the source LUNs - a RLP gets assigned as soon as you add the secondary image, and one of the mirror when the sync is running. When sync is complete, the RLP is released from the secondary image.
For snapshots - you will need to stop the session for each snap to release the RLP.
Incremental SNA Copy - the RLP is used to track all changes on the source LUN - will need to destroy the SAN Copy session to release the RLP.
Remember that if you are using snapshots that there is a minimum size for RLP based on the largest source LUN - I believe it's 2% - so if you snap a 2TB LUN, you will need to have a 200GB RLP - but you can not manually assign RLP from the pool. when a snap session starts it will take the next available RLP.
Reserve LUNs
White Paper: EMC CLARiiON Reserved LUN Pool Configuration Considerations - Best Practices Planning
RRR
6 Operator
•
5739 Posts
443
0
Posted September 24th, 2009 06:00
So after you created new ones on FC, take out 1 unused SATA LUN and put in a new one. Do this for all SATA RLP LUN's. You will run into SATA LUN's that are in use.... at a given point in time you'll need to shut down MV for a minute or so, but I think you'll manage to replace them all by hand.