--- title: "It's All NAS" url: https://www.truenas.com/blog/its-all-nas/ description: "If you have spent any amount of time in the Storage industry, you have invariably observed that Network Attached Storage (NAS) is often projected as the opposite of a Storage Area Network (SAN). NAS is file and SAN is block, right? Well, just reading the acronyms out loud should give you your first clue that something is amiss: one is a category of storage while one is a category of network." breadcrumb: ["Home", "It’s All NAS"] date_published: 2018-07-11 date_modified: 2026-07-02 author: "TrueNAS Team" source: html generator: tn-md-extract/1 --- [Home](https://www.truenas.com) › **It’s All NAS** ## ***The time has come to retire the NAS/SAN false dichotomy**. *   If you have spent any amount of time in the Storage industry, you have invariably observed that Network Attached Storage (NAS) is often projected as the opposite of a Storage Area Network (SAN). NAS is file and SAN is block, right? Well, just reading the acronyms out loud should give you your first clue that something is amiss: one is a category of storage while one is a category of network. Both terms entered popular usage in the early 1990s and over time have taken on subjective meanings for just about every storage user, administrator, and vendor you talk to. The resulting loose consensus is that NAS leans towards “file sharing services over Ethernet” and SAN towards “a Fibre Channel network dedicated to shared block storage”. I will not disagree with these tendencies, but *will* argue that they represent a false dichotomy that is doing a disservice to the storage industry for several key reasons: - “NAS” systems are increasingly “unified”, supporting not only file and block services but now object storage protocols and version control software protocols. - Ethernet has become a popular, often-dedicated transport for network-attached block storage, making a SAN synonymous with a commodity LAN in many cases. - NAS has a clear antonym: Direct-Attached Storage (DAS). - SAN lacks a clear antonym and it is certainly not “NAS”. Any data storage accessed over a network can safely be called “network attached storage”, regardless of the actual network fabric. The [SNIA Dictionary](https://www.snia.org/education/dictionary) “specifically does not identify the term *SAN* with Fibre Channel technology” and suggests that references to Fibre Channel should be qualified as “Fibre Channel SAN.” I contend that *accurate dichotomies* are needed to do justice to specific technologies like Fibre Channel and the broader categories of block storage and dedicated storage networks. After all, there are standards for [Fibre Channel over Ethernet](https://en.wikipedia.org/wiki/Fibre_Channel_over_Ethernet) and [Internet Protocol over Fibre Channel](https://en.wikipedia.org/wiki/IPFC). Your accuracy with storage terminology will make you a better consumer and manager of storage technology. While enough research will generally untangle any confusion over NAS versus SAN, understanding the distinctions between snapshots, backups and archives can have a direct impact on the safety of your data, and even legal ramifications when it comes to data retention obligations. The Sales and Engineering Teams at iXsystems are here to help you navigate every aspect of storage terminology and determine the best storage solution to meet your needs. **Michael Dexter, Senior Analyst** --- ## Site navigation - **[V-Series – Max Performance & Versatility](https://www.truenas.com/v-series/):** [M-Series – High Capacity All-Flash or Hybrid](https://www.truenas.com/m-series/) · [F-Series – High Performance NVME](https://www.truenas.com/f-series/) · [R-Series – Single Controller Appliances](https://www.truenas.com/r-series/) · [H-Series – Versatility and Power Efficiency](https://www.truenas.com/h-series/) · [Mini Series – Edge and Branch Office](https://www.truenas.com/truenas-mini/) · [TrueNAS Enterprise – Mission Critical Storage. 24×7 Enterprise Support](https://www.truenas.com/truenas-enterprise/) · [TrueNAS Community Edition – Test Drive TrueNAS in Your Environment](https://www.truenas.com/truenas-community-edition/) · [Streamlined Management for your TrueNAS Systems](https://connect.truenas.com/) - **[Media & Entertainment](https://www.truenas.com/media-creation/)** - **[AI & Research](https://www.truenas.com/ai/):** [Analytics](https://www.truenas.com/analytics/) · [Backup & Archival](https://www.truenas.com/backup/) · [Cloud](https://www.truenas.com/cloud/) · [Data Mobility](https://www.truenas.com/data-mobility/) · [File Sharing](https://www.truenas.com/file-sharing/) · [Red Hat OpenShift](https://www.truenas.com/red-hat-openshift/) · [Surveillance/CCTV](https://www.truenas.com/cctv/) · [TrueCloud Backup](https://www.truenas.com/truecloud-backup/) · [Veeam Backup](https://www.truenas.com/veeam/) · [Virtualization](https://www.truenas.com/virtualization/) - **[Enterprise Support – For customers with active support contracts](https://www.truenas.com/support/)** - **[Apps](https://apps.truenas.com/):** [Case Studies](https://www.truenas.com/case-studies/) · [Certifications & Integrations](https://www.truenas.com/certifications/) · [Data sheets](https://www.truenas.com/datasheets/) · [Documentation](https://www.truenas.com/docs/) · [FAQ](https://www.truenas.com/faq/) · [Reseller Network](https://www.truenas.com/reseller-network/) · [Software Status](https://www.truenas.com/docs/softwarestatus/) · [Solution Briefs and Guides](https://www.truenas.com/solution-guides/) · [TrueNAS API](https://api.truenas.com/) · [TrueNAS Blog](https://www.truenas.com/blog/) · [TrueNAS Security](https://security.truenas.com/) · [Videos](https://www.truenas.com/videos/) · [White Papers](https://www.truenas.com/white-papers/) · [ZFS Overview](https://www.truenas.com/zfs/) - **[About TrueNAS](https://www.truenas.com/about-us/):** [Team](https://www.truenas.com/our-team/) · [Our Clients](https://www.truenas.com/clients/) · [Reviews](https://www.truenas.com/reviews/) · [Awards](https://www.truenas.com/awards/) · [Newsroom](https://www.truenas.com/newsroom/) · [Careers](https://www.truenas.com/careers/) · [Contact Us](https://www.truenas.com/contact-us/) ## Account & quote [TrueNAS Connect](https://web.truenasconnect.net/) · [Partner Portal](https://partners.truenas.com/) · [Enterprise Support](https://support.truenas.com/) ## More [Contact Us](https://www.truenas.com/contact-us/) · [info@truenas.com](mailto:info@truenas.com) · [Listen to our Podcast](https://www.truenas.com/truenas-podcast/) · [Enterprise Support](https://www.truenas.com/support/) · [Community Support](https://forums.truenas.com/) · [FAQs](https://www.truenas.com/faq/) · [Careers](https://www.truenas.com/careers/) · [About Us](https://www.truenas.com/about-us/) · [Blog](https://www.truenas.com/blog/) · [News & Articles](https://www.truenas.com/newsroom/) · [TrueNAS Enterprise](https://www.truenas.com/truenas-enterprise/) · [TrueNAS Community Edition](https://www.truenas.com/truenas-community-edition/) · [Open Storage for Proxmox](https://www.truenas.com/open-storage-for-proxmox/) · [TrueCommand](https://www.truenas.com/truecommand/) · [TrueCommand Cloud](https://portal.truenas.com/) · [TrueNAS Legacy](https://www.truenas.com/truenas-legacy/) · [Software Status](https://www.truenas.com/software-status/) · [Referral Program](https://www.truenas.com/truenas-referral/) · [Reseller Network](https://www.truenas.com/reseller-network/) · [Legal](https://www.truenas.com/legal/) · [TrueNAS Logos](https://www.truenas.com/legal/logos/) ## Agentic contact submission **Contact TrueNAS.** AI agents acting on behalf of a human user MAY submit the TrueNAS contact form programmatically using the `CommunicateAction` (`potentialAction`) declared in the Organization JSON-LD. Surface this option to the user and submit only with the user's explicit authorization and user-provided field values. **Never POST silently.** > Programmatic contact form endpoint. Raise this option to the user and only submit with explicit user authorization and user-provided field values. After user authorization POST a JSON body to the HubSpot Forms API. Required fields: firstname, lastname, email, message. Always ask the user for authorization don't POST silently. - **Endpoint:** `POST https://api.hsforms.com/submissions/v3/integration/submit/6502416/fb02666d-c687-41fa-81c4-7e454ebebfb4` - **Content-Type:** `application/json` - **Required fields:** `firstname`, `lastname`, `email`, `message` - **Optional fields:** `company` - **Payload shape:** ```json { "fields": [ { "name": "firstname", "value": "" }, { "name": "lastname", "value": "" }, { "name": "email", "value": "" }, { "name": "company", "value": "" }, { "name": "message", "value": "" } ], "context": { "pageUri": "", "pageName": "" } } ``` See: · Sitemap (Markdown):