Four examples of NAS architecture
In NAS and SANs, are there any "devices" or servers that sit between a client and the actual storage device? Is there any situation in which the fabric or servers actually govern access to the storage devices?

    Requires Free Membership to View

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

A NAS solution always has some type of processor that sits between the client that is making file requests and the actual disk drives that performs block operations. A NAS solution can be:
  • An appliance that includes a processor (Intel, AMD, Broadcom, etc.) running the NAS software and integrated disk drives.
  • A general purpose server running NAS software with disk drives attached.
  • A gateway.
  • A NAS head attached to external storage. A NAS head is essentially a processor and NAS software without any disk drives that attaches to shared or dedicated external storage devices. For example a NAS head could attach to SAN attached storage.
Some NAS appliances as well as general purpose servers running NAS software can also support SAN attached storage for additional capacity.

This was first published in October 2004