Creating and allocating storage as needed

One reader asks for advice for building a new SAN with Brocade switches. Should he carve up all the storage up front or build LUNs as they go along?

Should all LUNs on a SAN be the same size? We're building a new SAN with Brocade switches, W2K, AIX, Solaris and...

Linux servers and multiple RAID units based on CMD Titan controllers. We're faced with a choice of carving up all the storage up front so that all LUNs are the same size or building LUNs as we go along and making them whatever size is needed. What is recommended best practice in this situation? I would sit down and plan everything out upfront as far as what types of RAID are needed for which environments. Use a mixture of RAID5, RAID1 and RAID0+1 based on the needs of the applications on each OS.

Once you have your RAID types planned out, you will be able to figure out how much storage space will be lost to parity information. This will give you your base useable capacity. Next you will need to determine how much more space is wasted after a file system is applied to your LUNs. This will give you your true useable capacity. Once everything is planned out and you're sure you have enough room for all your data, then you can plan how to partition your disks for allocating capacity. If your storage arrays are limited in cache size, then it would be best practice to lay out your storage so that each application uses it own separate physical disks. This will be easy to do with the multiple arrays your talking about. Spread the I/O load around as much as possible.

All that being said, and all your plans in place, if your storage array will let you create LUNs and partition them on the fly, then allocate the storage down the road as needed. This is because even the best laid out plans have a tendency, in our business, to change overnight due to some unforeseen application needing to be added. Creating and allocating storage as needed, will give you greater flexibility down the road. Of course, if you need to reboot the array every time a RAIDSET is added and formatted, then do it all up front.

Editor's note: Do you agree with this expert's response? If you have more to share, post it on ITKnowledgeExchange.com.

This was first published in January 2003

Dig Deeper on Primary storage capacity optimization



Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:



  • Tintri VMstore T5000

    Like all of its VM-aware storage systems, Tintri’s first all-flash array -- the Tintri VMstore T5000 -- allows admins to bypass ...

  • SolidFire SF9605

    The high-capacity SolidFire SF9605 uses SolidFire’s Element OS 8 (Oxygen) to deliver new enterprise features such as synchronous ...

  • HPE 3PAR StoreServ 20850

    HPE 3PAR StoreServ 20850 holds 1,024 solid-state drives (SSDs). Hewlett Packard Enterprise claims it can deliver more than three ...





  • Asigra Cloud Backup Version 13

    Asigra Cloud Backup Version 13 provides an AWS Elastic Block Store Snapshot Manager and the ability to support Docker container ...

  • Veeam Availability Suite v8

    Veeam Availability Suite v8 offers several key backup software components in one package, including Veeam Cloud Connect, Snapshot...

  • Druva inSync 5.5

    Druva inSync 5.5 endpoint backup software stands out with its proactive compliance, cloud app integration, full text search and ...