Ask the Expert [Video]: How to create a storage pool in VNX

Thank you for the video.  Could you discuss some best practice in regard to allocating LUNs per storage pool, and reasons to have multiple storage pools within a single VNX?

It is recommended to leave approximately 10% free space in the storage pool, to accommodate data services. The pool can still be over-subscribed above 100% of actual capacity; the 10% referenced here refers to actual free capacity that is not used in the pool.FAST VP requires free space to perform efficient relocations; it attempts to keep 10% free per tier.

VNX Snapshots requires at least 5% free to buffer snapped writes.

Block Deduplication uses free space to buffer write-splits.

Maintaining a total of 10% free will meet the requirements of all features.By default, the VNX2 will begin issuing alerts when more than 70% of available capacity has been subscribed. AVOID over-subscribing pools which contain thin LUNs for VNX File.

VNX File requires free space in the storage pool for normal functioning

General guidelines for storage pool LUNs for File

In general, when creating pool LUNs for use with File:

• Pre-provision space from the pool; create and assign LUNs to VNX OE for File,
• so that VNX OE for File has available space for file system creation and
• extension, snapshots, etc.
• Create approximately 1 LUN for every 4 drives in the storage pool
• Create LUNs in even multiples of 10
• Number of LUNs = (number of drives in pool divided by 4), rounded up to
• nearest multiple of 10
• Make all LUNs the same size
• Balance LUN ownership across SPA and SPB
• Apply the same tiering policies to all LUNs in the storage pool
• File-based space efficiency features are generally recommended over Block LUNbased
• space efficiency features:
• If Virtual Provisioning is required for VNX OE for File, use a thin- enabled file
• system on classic or thick LUNs
• If compression is required for VNX OE for File, use VNX OE for File
• Deduplication and Compression
• DON’T use compressed LUNs with VNX OE for File
• Block Compression is not supported with VNX OE for File LUNs
• If snapshots or checkpoints are required for VNX OE for File, use SnapSure.
• DON’T create VNX SnapShots on LUNs used by VNX OE for File

Jithin

Hi,

I'm wondering what would be the guideline to design and create a Storage Pool that will only be used for File. I wanted to know what points should I have in mind when creating the Storage Pool for file (things like lun size and quantity, thin or thick) to achive the best performance.

Hope you guys can give me some help.

Thanks in Advance!

Please see the VNX best practices for performance document for guidance on storage config for VNX file