Network attached storage managementHigh availability network attached storage clustering <<previous|next>>
Scale capacity with clustered NAS gateways
By Jerome Wendt
Clustered network attached storage (NAS) gateways are servers that sit in the data path between client servers and the storage arrays they access; the gateway acts as one logical server. A clustered file system (CFS) clusters together the different NAS gateway servers so that each gateway can access storage anywhere in the cluster. This configuration allows the use of installed storage resources and offers more options to independently scale storage capacity. How well each product does this largely depends on how the vendor has implemented its CFS to manage cache coherency among the different nodes.
Exanet's architecture is similar to clustered storage systems that use a parallel file system. Because ExaStore stores the file in 1 MB extents, this permits the controlling node to engage other nodes to read the 1 MB file extents in parallel more quickly. The other nodes then send their reads to the controlling node, which aggregates all of the 1 MB extents into the original file format. Once the file is assembled, it sends the file to the node that received the client request. This node then presents the file to the client.
The CFS on ONStor's Bobcat Series NAS Gateway seeks to avoid the whole problem of cache coherency by turning off the write cache in its clustered servers. Turning off the write cache forces all writes to go directly to back-end storage. This puts a lock on the file as writes occur and prevents reads or writes on other clustered servers from taking place until the write is complete. This approach works reasonably well for computing environments where different files are accessed randomly by different clients. And because ONStor supports multiple storage arrays from different vendors, users can match each file's performance and availability characteristics to the back-end storage.
But clustered NAS gateway architectures can only be deployed in circumstances where clients will access files over Ethernet interfaces using NFS or CIFS protocols. Using these protocols introduces overhead on both the requesting server and the NAS gateway server processing the request. While additional servers can be added to the cluster to provide the additional cache and CPU needed to handle these requests, it still isn't likely to satisfy the most performance-intensive, random-read applications that need to share files among the same or different operating systems. In these circumstances, users will need to look to a CFS that operates at the host level.
Check out the complete article from Storage magazine.
07 Mar 2007
Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.