Separate pool for file - reasons?

One thing that springs to mind is that FASTCache should not be used with the savvol for checkpoints

HTH

Gearoid

Hi Gearoid,

I agree with you.....for this particular case.

What about case when I use homogenous pool, no FAST, no FAST Cache, no other advanced features?

There must be some simple reason why not to mix it together.....

L.

One of the other reasons is single point of failure at the storagepool level or raid level within the pool

regards

Gearoid

Block Dedupe and Block Compression is not supported with VNX OE File LUNs

Good paper to read

VNX Unified Best Practices for Performance Applied Best Practices Guide

you will hear EMC talk about separating workloads because block workload is typically small size i/o and random and your typical NAS shares could be much larger i/o size and sequential ..and how this might have negative impact on system cache utilization. Honestly in my shop i use the same storage pool for block and file, my file workload is very modest so i have not seen any negative impact in performance. But you know EMC, you open a ticket about performance issue and they see that you are sharing that pool, they will use that as an excuse to blame that, whether is has anything to do with your issue. I am willing to fight that battle, so be prepared

Finally! Thanks for sharing your own experience.

Lukas.

Hi guys,

thaks for your answers. Unfortunately both of you considering usage of the advanced features which avoid mixing file and block on one storage pool. I read the whitepaper Dynamox adviced. Very nice one, but still lack of explanation of the best practice.....

What is the situation in simple config - NO advanced features, one homogenous pool. Should I still avoid mixing file and block? Why?

Thx.