Welcome to our new Ask the Expert video approach. On this thread we’re introducing a How-To Support video and an EMC Subject Matter Expert. We invite you to watch and post any questions, thoughts or feedback, based on the topic at hand. During the time this event is live our assigned SME (s) will be answering your inquiries as they get posted. After the assigned period has ended we'll leave it open so that everyone in the community can collaborate.
Here is your featured How-To video
Share this event on Twitter or LinkedIn:
>> Ask the Expert [Video]: How to create a storage pool in VNX http://bit.ly/1oWpyi9 #EMCATE <<
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?
Thanks for your query,
Creating multiple storage pool creates a Separate workloads with different I/O profiles,Vary pool parameters, such as Multicore FAST Cache enabled/disabled,Dedicate resources, when you have specific performance goals etc.
You can refer the document EMC VNX2 Unified Best Practices for Performance for more details about using multiple storage pools and also the best practices while creating storage pools.
Please refer page number 17 of the document.It gives you a detailed decription about storage pool expansion and pool capacity considerations.
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:
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!