I'd like some opinions on recommended LUN sizes and limits etc.
Obviously most of it will depend on what they are used for.
In our environment most LUN sizes are created as 1Tb.
What are the benefits/drawbacks from this?
And what about one big LUN compared with a metalun spanning smaller LUN.
A bit hard to give characteristics as we have all kinds of flavours.
A big one would be VMware ESX 3.5 that stores all its VMs on the SAN. Other than that Windows file servers that store users data. Another thing I expect to pop up soon is SQL database storage.
Remember that ESX has a VMFS limit of 2TB and that is 2047GB. If you try to create a 2TB one, it's invisible for ESX (I tried that). Furthermore consider using RDM (Raw Device Mappings), so a VM get's a true Clariion LUN and not just a piece of a larger VMFS. For performance reasons you should consider spreading the load accross as many physical spindels as possible, however: larger RAID Groups have considerably longer "repair" times if a hot spare is invoked, since more disks need to be read to rebuild the missing data. Consider using METALUN's with RG's of 5 spindels (4+1). Each RG has it's own HS and rebuild times will be fair. If performance is not a big issue, use RAID5 (8+1), but remember that rebuild times will be longer.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
762
0
Posted April 17th, 2008 16:00
can you give some info like OS , volume manager , application, replication requirements ..etc