Global Namespace and the Path to NAS 2.0

In the little over a year that we have been shipping our FXT Scale-out NAS Appliance, we have received very positive feedback on our product and its ability to scale NAS performance.  Performance scaling is the result of both our Tiered File System (TFS), which dynamically allocates frequently used blocks to faster storage media, and our clustering technology which clusters up to 25 appliances together to linearly scale performance.

Our primary objective has been to increase NAS efficiency by off-loading filer operations and facilitating the use of high density, low power media for mass bulk storage.  It is common for our customers to perform the same or more processing as traditional NAS with 1/5th of the data center resources (rack space, power & cooling).

Our customers typically characterize our product as the “user or client facing side of NAS” and the traditional filer as the “archive or data management part”.  The most frequent request from our customers has been “Now that you implement the client facing side of NAS, can you do something to help with our NAS clutter?”

NAS Clutter

Storage administrators traditionally have scaled their environment first by adding expensive, power hungry and low density performance disks behind a single filer until that filer becomes over loaded, and second by adding more filers to their environment.  Over time, this results in NAS clutter – a multi-filer environment in which the user or client machines must be aware of (and re-configured with) any changes in the storage environment.
http://averesystems.filhttp://averesystems.files.wordpress.com/2011/03/nas1-0clutter.png?w=400&h=290&h=200
Click here for the full-sized image

NAS clutter is the result of the current NAS 1.0 architecture that was not built to scale performance or handle the challenges of geographically distributed users.  The NAS filer is the single bottleneck in the NAS environment – all operations from all users must transit the filer, much like single CPU processors were the bottleneck in computers until the advent of multi-core architectures.  The NAS 1.0 architecture worked well a decade ago but has severe limitations today.

http://averesystems.filhttp://averesystems.files.wordpress.com/2011/03/nas1-0architecture2.png?w=400&h=290&h=200
Click here for the full-sized image

Towards NAS 2.0

In our product announcement last week, we introduced global namespace, or GNS, functionality to the FXT product line.  Using GNS our customers can now create a single logical namespace in the FXT cluster, which is visible to all clients that mount any FXT Appliance.  The storage administrator can then configure any export on any filer in their data center to be a sub-tree within that namespace.  A single common view is presented to all users or clients, effectively eliminating NAS clutter.
http://averesystems.filhttp://averesystems.files.wordpress.com/2011/03/nas2-0.png?w=400&h=290&h=200
Click here for the full-sized image

Global namespace and the virtualization of storage resources is an important building block for scaling out the NAS architecture.  When you combine global namespace with Avere’s dynamic media tiering and scale-out clustering you have the genesis of NAS 2.0:

  • Global namespace removes NAS clutter from the user view – separating the client facing NAS services from datacenter administration.
  • Dynamic media tiering and scale-out clustering hide mass storage and WAN latency, facilitating the use of high density (low cost, low power) media and remote Cloud storage.

NAS 2.0 and Cloud Storage

NAS 2.0 provides the right combination of global namespace and performance scaling to finally make cloud storage a reality for enterprise applications.  Current cloud storage deployments are typically relegated to backup and data protection applications, due to the high latency to transit the WAN.  Because of that latency, enterprise application performance would suffer and live users would see unacceptably high latency to their data.

Avere’s performance scaling permits enterprise applications and end users to access remote storage with no degradation in performance over local storage.  The deployment model places an Avere FXT cluster near enterprise applications or end users.  Storage can be located anywhere.  The added benefit of GNS in this model is that storage components can be located at several locations with a single access point for all users at all locations – creating a single view of storage for distributed enterprises.  GNS effectively hides the additional clutter of multiple locations for these distributed enterprises.

In summary, GNS is a fundamental component of a NAS 2.0 architecture, whether its within the data center, in the cloud or a hybrid of both. In my next post, I’ll explore more fully how NAS 2.0 enables cloud access.


Post a Comment

Required fields are marked *

*
*

Follow

Get every new post delivered to your Inbox.