{"id":96847,"date":"2023-08-29T10:32:57","date_gmt":"2023-08-29T10:32:57","guid":{"rendered":"https:\/\/www.techopedia.com\/?post_type=q-a&p=96847"},"modified":"2023-08-29T10:32:57","modified_gmt":"2023-08-29T10:32:57","slug":"whats-the-difference-between-nas-and-san","status":"publish","type":"q-a","link":"https:\/\/www.techopedia.com\/experts\/whats-the-difference-between-nas-and-san","title":{"rendered":"What’s the Difference Between NAS and SAN?"},"content":{"rendered":"
NAS<\/a> and SAN<\/a> \u2013 the N in both these palindromic acronyms stands for network<\/a>. They’re closely related in that SAN is the hen house, and NAS is the hens.<\/p>\n In other words, SAN is the network your NAS resides on. At least if the said network is dedicated solely to storage<\/a>.<\/p>\n That’s the simple answer, but as usual, there’s more to it.<\/p>\n NAS is short for Network-Attached Storage. It’s storage that uses network technology such as Ethernet<\/a> to transfer data rather than a direct connection to a computer<\/a> such as USB<\/a>, Firewire<\/a>, or Thunderbolt<\/a>. As such, it’s part and parcel of your network from the get-go.<\/p>\n NAS boxes are commonly accessed and administered via an HTML<\/a> interface, though you can use other network protocols<\/a> such as FTP<\/a>, WebDAV<\/a>, etc. For instance, you fire up your Web browser<\/a>, direct it to the box’s IP address<\/a> (E.g., 192.168.1.10), a GUI<\/a> will appear to facilitate changing settings, checking drive health and configuration, etc. This is sometimes referred to as In-Band Management, though for obvious reasons, it’s not shortened to IBM.<\/p>\n Most NAS boxes also allow Out-of-Band Management<\/a>\u00a0or OOBM. That’s a fancy way of saying you can attach a display<\/a>, keyboard<\/a>, and mouse<\/a> and use the NAS box just as you would a normal computer. It is indeed a computer. Just one dedicated to storage.<\/p>\n In fact, if a NAS box is in a rack, there’s a tendency to call it a server<\/a>. The distinction is generally meaningless these days, as once “dumb” NAS now offers a host of server functionality such as media streaming<\/a>, surveillance, website serving<\/a>, virtual computing (VMs<\/a>, Docker<\/a>, etc.), email hosting<\/a>, etc.<\/p>\n SAN is short for Storage Area Network. When I first heard the acronym, I thought it was simply the network that tied together my company’s workstations<\/a> in the storage area. After a rather strained look from my colleague, it was explained that was a separate network dedicated to all the company’s storage devices.<\/p>\n SAN can be as simple as several NAS boxes tied together, but it can also be a far more complex mix of transport and storage technologies. Hard drives<\/a>, SSDs<\/a>, tape carousels (yes, they still exist), iSCSI<\/a>, SAS<\/a>, Ethernet, fiber channel<\/a>, NVMe<\/a>, SATA<\/a>, etc. As long as you have the proper connections, controllers, interconnects, protocol translators<\/a>, etc., to render the storage visible over the network, it’s all good.<\/p>\n For a SAN to take the leap from network-connected storage to an actual storage network, there has to be firmware<\/a> or software<\/a> to define and administer it. Just as multiple drives in a NAS box are tied together by RAID<\/a> or the equivalent into larger logical units, the devices on a storage area network are abstracted into larger storage pools. For instance, you could treat three different 24TB<\/a> NAS boxes as one logical 72TB storage unit.<\/p>\n However, you can take it a lot further. For instance, you could use a pool of SSDs for caching<\/a> and fast transactions, a pool of hard drives for longer-term storage, and a pool of tape drives for archiving or backup<\/a>. No matter the topology, just like any network entity, SAN allows multiple simultaneous connections. I.e., anything or anyone with access to the network can utilize it.<\/p>\n Usually, all the SAN hardware will be in one location on one local network<\/a>, although there’s nothing to say you can’t use geographically separated hardware if you have a wide enough pipe.<\/p>\nWhat is NAS?<\/span><\/h2>\n
What is SAN?<\/span><\/h2>\n