Transactional NAS is the category that encompasses workloads, like server virtualization and databases, that have traditionally been directed toward block storage but where we’re seeing customers start to embrace file protocols. More and more applications such as Oracle, SQL, SAP, VMware, and VDIs are being run over NAS.
In this Ask the Expert event, we’ll discuss how the next-generation VNX with MCx demonstrates the following benefits for transactional applications run over NAS:
Kaushik Ghosh is manager of EMC's Unified Storage Division Product Management team. His expertise is in VNX and NAS.
This discussion will be moderated through September 16. Follow the thread in your inbox (see option on right) to receive updates!
My questions for the expert session:
- How does performance (i.e. responstime) benefit if file is an additional layer on top of block?
- How can we manage mixed I/O profiles? (DB, VDI, Office) Can filepools be shared for different workloads?
- How can we assure single-stream-sequential-bandwith-apps with guanteed MB/sec in mixed enviroments?
- How to size storage, memory and protocols?
- How can a transactional db with a app which needs a guaranteed low responstime survive a VNX2 datamover failure? What are the minimum failover times for datamovers in VNX2?
- How to backup DB/VMware environments on file efficiently?
JP - Thanks for the feedback. Here is my response to the questions you posted ...
1. Our file response time for VM workloads is 60% faster with the new VNX.
2. Yes file pools can be shared between different workloads
3. Unfortunately there is no way to guarantee performance today. We are looking at QoS for a future release.
4. We have tools that help with sizing (VNX sizer as an example)
5. VNX DM failover time can be less than 30 secs to up to 90 secs for small-medium number of file systems. In a VMware environment - typically the number of file systems is not very high (each fs maps to a VM data store).
6. RM and AppSync supports VM consistent snaps of the entire NFS data store. You can then backup the snap, or keep the snaps around and use the snap as the first line of defense. We support up to 96 snaps per NFS data store.
Transactional applications like VMware or databases running on VMware typically require low response time. Traditionally these applications used to run on block. As performance (IOPS and response time) and availability of NAS gets better - more customers would move their transactional applications (at least the ones which do not require the best IOPS/response time) to run on NAS.
looks like like File OE is identical to 7.1 from feature set stand point ..it just now runs on faster block hardware. Looking forward to the next version of File OE.
There are a bunch of features in VNX OE 8 --- and more are planned in 2014. For example, VDMs is an area we have made enhancements and will continue to enhance through 2014.
What is Your reccomendation for setting up storage on the Next gen VNX using NFS for Vmware.
thin on the Array or let Vmware do the thin provisioning