What you will learn from this tip: NAS
Managing files has become a big headache for enterprises. How should the files be stored, and on what tier of disk? And are there other considerations, such as legal regulations pertaining to the disposition of the files? Consolidating disparate NAS filers behind a NAS appliance gateway offers companies an effective way to scale file systems and manage back-end storage arrays, but it also creates its own set of problems. As NAS gateways move off the array and into the network, organizations must start to plan how best to use them.
A NAS head appears in the network in one of two ways. In the traditional sense, it ships as part of a larger storage subsystem with its own set of disk, such as Network Appliance (NetApp) Inc.'s FAS980. A NAS head can also appear as a standalone appliance, such as NetApp's gFiler that functions as a gateway to connect storage arrays of different tiers and even different vendors. These gateway products generally use Fibre Channel (FC) to connect to back-end arrays.
Using one central NAS head to consolidate existing NAS filers creates the following issues:
Support for the iSCSI protocol allows organizations to use NAS heads for file- and block-based services. The ability to dynamically re-stripe data across back-end arrays lets administrators optimize the performance of new and existing data. And as more NAS head vendors support and certify different vendors' arrays, users no longer need to lock themselves into a particular vendor's array. Many NAS head vendors now support multiple tiers of back-end storage along with policy management tools that allow aging files to be transparently migrated from one tier of storage to another. With so many options available, users need to distinguish between required and optional features on NAS heads. The must-have list includes:
In addition, organizations should consider the following features as they plan for the future:
Read more of this tip in Storage magazine.
For more information:
About the author: Jerome M. Wendt (email@example.com) is a storage analyst specializing in the field of open-systems storage and SANs. He has managed storage for small- and large-sized organizations in this capacity.
This was first published in April 2005