This post is more than 5 years old
5 Posts
0
626
Reserved LUN Pool Used!
I am new to world of Clariions and our main EMC guy is on holida at the moment! We have 2 Clariion CX380's on 2 sites that replicate to each other using MIrrorview. The reserved LUN pool has filled up on the DR site side and I am unsure what to do to best resolve this. Can anyone point me in the right direction? I would rather avoid creating more LUN's for the pool if possible as I can't follow the layout set by our in house Clariion expert as the RAID group the current LUNs come from has no spare capacity.
Is there a way to stop and start replication thus releasing current LUN's without causing a complete resync? Out guy is back oin Monday so a short term fix would be ideal.
Thanks,
Sam
AranH1
2.2K Posts
0
April 9th, 2010 05:00
Sam,
The easiest short term fix would be to add more LUNs to the reserved LUN pool. The LUNs added to the RLP do not have to be from the same RAID Group, they can come from any group really, I would just create some more LUNs of the same size that your guy used to previously populate the RLP (usually a standard size is used). The additional LUNs can always be removed later after the cause of the RLP filling up has been resolved. This will also buy you the time needed to troubleshoot the issue with causing replication processes to halt (hopefully).
After the RLP has more space, the next step would be to determine why the RLP is filling up.
Aran
srudders
5 Posts
0
April 9th, 2010 05:00
Thanks for that - I have added some more LUNs to the RLP now and the mirroring is running again. What would I need to do to try and figure out why the RLP is filling? I'm on call this weekend and would rather not be called out in the middle of the night if the RLP fills again!
Thanks,
Sam
Sam Rudland | UNIX\Storage Team Lead | ING Direct
2 Callaghan Square, Cardiff, CF10 5AT
Tel: 02920 358514l Email: sam.rudland@ingdirect.co.uk
AranH1
2.2K Posts
1
April 9th, 2010 06:00
Unfortunately I am not familiar with MirrorView, all my experience has been with SAN Copy and SnapView. But you should be able to check a few things on the array that could give you an indication of what is using the RLP. In Navisphere if you right-click on the array you should see towards the bottom a few items like SAN Copy, SnapView, Analyzer, and MirrorView. I know that with SAN Copy and SnapView if I select these items one of the items on the sub menu is a session summary selection. MirrorView should have something similar. I would check that first. If you do have SnapView and SAN Copy I would check their session summaries as well. At a minimum this may show you which LUNs (or snapshots) are involved in your replications that are causing the rise in RLP usage.
Hopefully someone with MirrorView experience can chime in here and give you more guidance.
kelleg
4.5K Posts
0
April 9th, 2010 08:00
There are a couple of things that can use up all your RLP:
1. too many snap sessions running
2. too much Write activity on the source LUNs for the mirrors - maybe someone kicked off a defrag - that could case a re-write to all sectors on the source LUN, which would require writing all new sectors on the mirror - and any snaps you had running -
Rhe RLP is used to keep all the Copy-On-First-Writes to the source LUN - if you re-org a database or do a defrag, that could touch all the sectors which could trigger a COFW that could fill up all the RLP.
glen