SAN vs. NAS: A diagram of the differences

SAN vs. NAS: A diagram of the differences

I would like to know about the differences in SAN and NAS with the help of a diagram. Also please suggest where to position a SAN and NAS. How do you decide whether to use a SAN or NAS?

    Requires Free Membership to View

    Login

    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.

 

Basically, a SAN does block I/O just like having a disk directly attached to a server. A NAS is really remote file system I/O where the file request is redirected over a network to a device (really a processing entity with its own file system) where the file I/O is actually performed. Here are two pictures that give you a general idea of how the I/O is done between block (SAN) and remote file I/O (NAS):

Deciding whether to use a SAN vs. NAS has many factors to consider so there's not a specific answer. In general if your application requires block I/O or there is a significant performance requirement, use a SAN. If it's file based I/O for the application or you need to share files and you want simple administration, use NAS.

This was first published in December 2005