Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Network-attached storage
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Computer data storage server}} {{redirect-distinguish|NAS (computing)|network access server}} {{More citations needed|date=September 2024}} [[File:NAS_server.png|thumb|A five-bay NAS server]] '''Network-attached storage''' ('''NAS''') is a file-level [[computer data storage]] server connected to a [[computer network]] providing data access to a [[Heterogeneous computing|heterogeneous]] group of clients. In this context, the term "NAS" can refer to both the technology and systems involved, or a specialized [[computer appliance]] device unit built for such functionality β a ''NAS appliance'' or ''NAS box''. NAS contrasts with [[block-level storage|block-level]] [[storage area network]]s (SAN). ==Overview== A NAS device is optimised for [[file server|serving files]] either by its hardware, software, or configuration. It is often manufactured as a [[computer appliance]]{{snd}} a purpose-built specialized computer. NAS systems are networked appliances that contain one or more [[hard disk drive|storage drives]], often arranged into [[logical disk|logical]], redundant storage containers or [[RAID]]. Network-attached storage typically provide access to files using network file sharing protocols such as [[Network File System (protocol)|NFS]], [[Server Message Block|SMB]], or [[Apple Filing Protocol|AFP]]. From the mid-1990s, NAS devices began gaining popularity as a convenient method of sharing files among multiple computers, as well as to remove the responsibility of file serving from other servers on the network; by doing so, a NAS can provide faster data access, easier administration, and simpler configuration as opposed to using general-purpose server to serve files.<ref>{{Cite web|url=http://www.infostor.com/index/articles/display/55961/articles/infostor/volume-2/issue-4/news-analysis-trends/nas-advantages-a-vars-view.html|title=NAS advantages: A VARs view|website=www.infostor.com|date=April 1, 1998|access-date=26 February 2019|first=Ron|last=Levine}}</ref> Accompanying a NAS are purpose-built [[hard disk drive]]s, which are functionally similar to non-NAS drives but may have different firmware, vibration tolerance, or power dissipation to make them more suitable for use in RAID arrays, a technology often used in NAS implementations.<ref>{{cite web|title=Marketing bulletin: NAS versus desktop - Evaluating HDDs for NAS applications|url=http://www.seagate.com/files/www-content/product-content/nas-fam/nas-hdd/en-us/docs/nas-vs-desktop-marketing-bulletin-mb633-1-1304us.pdf|website=seagate.com|access-date=29 December 2021}}</ref> For example, some NAS versions of drives support a command extension to allow extended error recovery to be disabled. In a non-RAID application, it may be important for a disk drive to go to great lengths to successfully read a problematic storage block, even if it takes several seconds. In an appropriately configured RAID array, a single bad block on a single drive can be recovered completely via the redundancy encoded across the RAID set. If a drive spends several seconds executing extensive retries it might cause the RAID controller to flag the drive as "down" whereas if it simply replied promptly that the block of data had a checksum error, the RAID controller would use the redundant data on the other drives to correct the error and continue without any problem. == Description == A NAS unit is a computer connected to a network that provides only file-based data storage services to other devices on the network. Although it may technically be possible to run other software on a NAS unit, it is usually not designed to be a general-purpose server. For example, NAS units usually do not have a keyboard or display, and are controlled and configured over the network, often using a browser.<ref>{{cite magazine|title=An introduction to network attached storage|magazine=HWM Singapore|date=July 2003|issn=0219-5607|publisher=SPH Magazines|pages=90β92}}</ref> A full-featured operating system is not needed on a NAS device, so often a stripped-down operating system is used. NAS systems contain one or more hard disk drives, often arranged into logical, redundant storage containers or [[RAID]]. NAS uses file-based protocols such as [[Network File System (protocol)|NFS]] (popular on [[UNIX]] systems), SMB ([[Server Message Block]]) (used with [[Microsoft Windows]] systems), [[Apple Filing Protocol|AFP]] (used with [[Macintosh|Apple Macintosh]] computers), or NCP (used with [[Novell Open Enterprise Server|OES]] and [[NetWare|Novell NetWare]]). NAS units rarely limit clients to a single protocol. === Comparing with DAS === The key difference between [[direct-attached storage]] (DAS) and NAS is that DAS is simply an extension to an existing server and is not necessarily networked. As the name suggests, DAS typically is connected via a [[USB]] or [[Thunderbolt (interface)|Thunderbolt]] enabled cable. NAS is designed as an easy and self-contained solution for sharing files over the network. Both DAS and NAS can potentially increase availability of data by using [[RAID]] or [[Computer cluster|clustering]]. Both NAS and DAS can have various amount of [[Cache (computing)|cache memory]], which greatly affects performance. When comparing use of NAS with use of local (non-networked) DAS, the performance of NAS depends mainly on the speed of and congestion on the network. Most NAS solutions will include the option to install a wide array of software applications to allow better configuration of the system or to include other capabilities outside of storage (like video surveillance, virtualization, media, etc). DAS typically is focused solely on data storage but capabilities can be available based on specific vendor options. === Comparing with SAN === [[File:SANvsNAS.svg|thumb|Visual differentiation of NAS and [[storage area network|SAN]] use in network architecture]] NAS provides both storage and a [[file system]]. This is often contrasted with SAN ([[storage area network]]), which provides only block-based storage and leaves file system concerns on the "client" side. SAN protocols include [[Fibre Channel]], [[iSCSI]], [[ATA over Ethernet]] (AoE) and [[HyperSCSI]]. One way to loosely conceptualize the difference between a NAS and a SAN is that NAS appears to the client OS (operating system) as a [[file server]] (the client can [[drive mapping|map]] network drives to shares on that server) whereas a disk available through a SAN still appears to the client OS as a disk, visible in disk and volume management utilities (along with client's local disks), and available to be formatted with a file system and [[Mount (computing)|mounted]]. Despite their differences, SAN and NAS are not mutually exclusive and may be combined as a SAN-NAS hybrid, offering both file-level protocols (NAS) and block-level protocols (SAN) from the same system{{citation_needed|date=May 2025}}. A [[shared disk file system]] can also be run on top of a SAN to provide filesystem services. == History == In the early 1980s, the "[[Newcastle Connection]]" by [[Brian Randell]] and his colleagues at [[Newcastle University]] demonstrated and developed remote file access across a set of UNIX machines.<ref name="Newcastle_1982">{{cite journal|title=The Newcastle connection|author-last1=Brownbridge|author-first1=David R.|author-last2=Marshall|author-first2=Lindsay F.|author-last3=Randell|author-first3=Brian|author-link3=Brian Randell|journal=Software: Practice and Experience|volume=12|year=1982|doi=10.1002/spe.4380121206|pages=1147β1162|s2cid=1840438 |url=http://www.cs.ncl.ac.uk/publications/articles/papers/399.pdf|access-date=16 August 2016|url-status=dead|archive-url=https://web.archive.org/web/20160816184205/http://www.cs.ncl.ac.uk/research/pubs/articles/papers/399.pdf|archive-date=16 August 2016}}</ref><ref name="Callaghan_2000">{{cite book|author-last=Callaghan|author-first=Brent|title=NFS illustrated|publisher=[[Addison-Wesley]]|year=2000|isbn=0-201-32570-5}}</ref> [[Novell]]'s [[NetWare]] server operating system and [[NetWare Core Protocol|NCP]] protocol was released in 1983. Following the Newcastle Connection, [[Sun Microsystems]]' 1984 release of [[Network File System|NFS]] allowed network servers to share their storage space with networked clients. 3Com and [[Microsoft]] would develop the [[LAN Manager]] software and protocol to further this new market. [[3Com]]'s [[3Server]] and [[3+Share]] software was the first purpose-built server (including proprietary hardware, software, and multiple disks) for open systems servers. Inspired by the success of [[file server]]s from Novell, [[IBM]], and Sun, several firms developed dedicated file servers. While 3Com was among the first firms to build a dedicated NAS for desktop operating systems, [[Auspex Systems]] was one of the first to develop a dedicated NFS server for use in the UNIX market. A group of Auspex engineers split away in the early 1990s to create the integrated [[NetApp FAS]], which supported both the Windows SMB and the UNIX NFS protocols and had superior [[scalability]] and ease of deployment. This started the market for [[Proprietary hardware|proprietary]] NAS devices now led by NetApp and EMC Celerra. Starting in the early 2000s, a series of startups emerged offering alternative solutions to single filer solutions in the form of clustered NAS{{snd}} Spinnaker Networks (acquired by [[NetApp]] in February 2004), [[Exanet]] (acquired by [[Dell]] in February 2010), [[Gluster]] (acquired by RedHat in 2011), ONStor (acquired by LSI in 2009), [[IBRIX Fusion|IBRIX]] (acquired by [[Hewlett-Packard|HP]]), [[Dell EMC Isilon|Isilon]] (acquired by EMC{{snd}} November 2010), PolyServe (acquired by [[Hewlett-Packard|HP]] in 2007), and [[Panasas]], to name a few. In 2009, NAS vendors (notably CTERA networks<ref name="cdr">{{cite web|url=http://cdrlab.pl/article_strona_9571_1.html|title=CDRLab test|archive-url=https://web.archive.org/web/20101017224312/http://cdrlab.pl/article_strona_9571_1.html|archive-date=17 October 2010|url-status=dead|language=pl}}</ref><ref>{{cite web|url=http://www.forrester.com/rb/Research/age_of_computing_diversity/q/id/56888/t/2|url-status=dead|archive-url=https://web.archive.org/web/20100926105633/http://www.forrester.com/rb/Research/age_of_computing_diversity/q/id/56888/t/2|archive-date=26 September 2010|title=The age of computing diversity|author=Frank E. Gillett|website=Forrester research|date=16 September 2010|page=12|quote=CTERAβs C200 provides a better take on network-attached storage (NAS) [...] with local Mac and PC backup built in and automated hooks to an online backup service for offsite backup in case of site disaster.}}</ref> and [[Netgear]]) began to introduce [[Remote backup service|online backup]] solutions integrated in their NAS appliances, for online disaster recovery.<ref>{{cite press release|url=https://www.reuters.com/article/pressRelease/idUS130761+02-Mar-2009+PRN20090302|archive-url=https://archive.today/20120908050357/http://www.reuters.com/article/pressRelease/idUS130761+02-Mar-2009+PRN20090302|url-status=dead|archive-date=8 September 2012|publisher=Reuters|title=Netgear launches first NAS-linked online disaster recovery for consumers and SMBs|access-date=21 October 2009}}</ref><ref>{{cite press release|url=https://www.reuters.com/article/pressRelease/idUS125181+06-Jan-2009+PRN20090106|archive-url=https://web.archive.org/web/20090307115844/http://www.reuters.com/article/pressRelease/idUS125181+06-Jan-2009+PRN20090106|url-status=dead|archive-date=7 March 2009|title=CTERA networks launches, introduces cloud attached storage|publisher=Reuters|access-date=21 October 2009}}</ref> By 2021, three major types of NAS solutions are offered (all with hybrid cloud models where data can be stored both on-premise on the NAS and off site on a separate NAS or through a public cloud service provider). The first type of NAS is focused on consumer needs with lower-cost options that typically support 1β5 hot plug hard drives. The second is focused on small-to-medium-sized businesses β these NAS solutions range from 2β24+ hard drives and are typically offered in tower or rackmount form factors. Pricing can vary greatly depending on the processor, components, and overall features supported. The last type is geared toward enterprises or large businesses and are offered with more advanced software capabilities. NAS solutions are typically sold without hard drives installed to allow the buyer (or IT departments) to select the hard drive cost, size, and quality. == Implementation == The way manufacturers make NAS devices can be classified into three types: # Computer-based NAS{{Spaced ndash}} using a computer (server level or a [[personal computer]]) with processors typically from Intel or AMD, installs FTP/SMB/AFP... software server. The power consumption of this NAS type is the largest, but its functions are the most powerful. Some large NAS manufacturers such as [[Synology]], [[QNAP Systems|QNAP systems]], and [[Asus]] make these types of devices. Max FTP throughput speed varies by computer [[Central processing unit|CPU]] and amount of RAM. # Embedded-system-based NAS{{Spaced ndash}} using an ARM- or MIPS-based processor architecture and a [[Real-time operating system|real-time operating system (RTOS)]] or an [[embedded operating system]] to run a NAS server. The power consumption of this NAS type is fair, and functions in the NAS can fit most end-user requirements. [[Marvell Technology, Inc.|Marvell]], [[Oxford Instruments|Oxford]], and Storlink make chipsets for this type of NAS. Max FTP throughput varies from 20 MB/s to 120 MB/s. # [[Application-specific integrated circuit|ASIC]]-based NAS{{Spaced ndash}} provisioning NAS through the use of a single ASIC chip, using hardware to implement TCP/IP and file system. There is no OS in the chip, as all the performance-related operations are done by hardware acceleration circuits. The power consumption of this type of NAS is low, as functions are limited to only support SMB and FTP. [[LayerWalker]] is the only chipset manufacturer for this type of NAS. Max FTP throughput is 40 MB/s. == Uses == NAS is useful for more than just general centralized storage provided to client computers in environments with large amounts of data. NAS can enable simpler and lower cost systems such as [[Load balancing (computing)|load-balancing]] and fault-tolerant email and web server systems by providing storage services. The potential emerging market for NAS is the consumer market where there is a large amount of multi-media data. Such consumer market appliances are now commonly available. Unlike their [[19-inch rack|rackmount]]ed counterparts, they are generally packaged in smaller form factors. The price of NAS appliances has fallen sharply in recent{{When|date=September 2024}} years, offering flexible network-based storage to the home consumer market for little more than the cost of a regular [[USB]] or [[IEEE 1394|FireWire]] external hard disk. Many of these home consumer devices are built around [[ARM architecture|ARM]], x86 or [[MIPS architecture|MIPS]] processors running an [[Linux on embedded systems|embedded Linux]] [[operating system]]. A '''purpose-built backup appliance''' (PBBA) is a kind of NAS intended for storing [[backup]] data. PBBAs typically include [[data deduplication]], compression, [[RAID 6]] or other redundant hardware components, and automated maintenance.<ref> Johnny Yu. [https://www.techtarget.com/searchdatabackup/definition/purpose-built-backup-appliance-PBBA "What is a purpose-built backup appliance (PBBA)?"]. </ref><ref> [https://www.veritas.com/information-center/purpose-built-backup-appliance-ultimate-guide "Purpose-Built Backup Appliance (PBBA): The Ultimate Guide"]. </ref><ref> [https://www.starwindsoftware.com/blog/purpose-built-backup-appliance/ "Purpose-Built Backup Appliance: Enhance Your Data Protection and Recovery"] </ref><ref> Hubert Brychczynski. [https://objectfirst.com/guides/data-storage/purpose-built-backup-appliance-pbba/ "Purpose-Built Backup Appliances (PBBA) - Features and Market Potential"]. </ref> A PBBA may also be called a '''[[backup and disaster recovery appliance]]''' or simply a '''backup [[computer appliance | appliance]]'''. == Examples == === Open-source server implementations === [[Open-source software|Open-source]] NAS-oriented distributions of [[Linux]] and [[FreeBSD]] are available. These are designed to be easy to set up on commodity PC hardware, and are typically configured using a web browser. They can run from a [[virtual machine]], [[Live CD]], [[booting|bootable]] USB flash drive ([[Live USB]]), or from one of the mounted hard drives. They run [[Samba (software)|Samba]] (an [[Server Message Block|SMB]] daemon), [[Network File System|NFS]] daemon, and [[File Transfer Protocol|FTP]] daemons which are freely available for those operating systems. === Network-attached secure disks=== '''Network-attached secure disks''' ('''NASD''') is 1997–2001 research project of [[Carnegie Mellon University]], with the goal of providing cost-effective scalable [[Computer data storage|storage]] [[Bandwidth (computing)|bandwidth]].<ref>{{cite web|url=http://www.pdl.cmu.edu/NASD/|title=NASD: Network attached secure disks}}</ref> NASD reduces the overhead on the file [[Server (computing)|server]] (file manager) by allowing storage devices to transfer data directly to [[Client (computing)|client]]s. Most of the file manager's work is offloaded to the storage disk without integrating the file system policy into the disk. Most client operations like Read/Write go directly to the disks; less frequent operations like authentication go to the file manager. Disks transfer variable-length objects instead of fixed-size blocks to clients. The File Manager provides a time-limited cachable capability for clients to access the storage objects. A file access from the client to the disks has the following sequence: # The client authenticates itself with the file manager and requests for the file access. # If the client can be granted access to the file requested, the client receives the [[Computer network|network]] location of NASD disks and their capability. # If the client is accessing the disk for the first time, it receives a time-limited key for the establishment of secure communication to the disk. # The file manager informs the corresponding disk using an independent channel. # From now on, the client directly accesses the NASD disks by giving the capability it received and further data transfers go through the network, bypassing the file manager. === List of network protocols used to serve NAS === {{div col|colwidth=27em}} * [[Andrew File System]] (AFS) * [[Apple Filing Protocol]] (AFP) * [[Server Message Block]] (SMB) * [[File Transfer Protocol]] (FTP) * [[Hypertext Transfer Protocol]] (HTTP) * [[Network File System]] (NFS) * [[rsync|{{mono|rsync}}]] * [[SSH file transfer protocol]] (SFTP) * [[Universal Plug and Play]] (UPnP) {{div col end}} == Clustered NAS == {{Main|Clustered file system}} A '''clustered NAS''' is a NAS that is using a distributed file system running simultaneously on multiple servers. The key difference between a clustered and traditional NAS is the ability to distribute{{citation needed|date=October 2012}} (e.g. stripe) data and [[metadata]] across the cluster nodes or storage devices. Clustered NAS, like a traditional one, still provides unified access to the files from any of the cluster nodes, unrelated to the actual location of the data. == See also == {{Div col|colwidth=27em}} * [[Disk enclosure]] * [[File virtualization]] * [[Global Namespace]] * [[List of NAS manufacturers]] * [[Network architecture]] * [[Server (computing)]] {{Div col end}} == References == {{Reflist|30em}} == Further reading == * [https://web.archive.org/web/20011226222438/http://www.pdl.cmu.edu/PDL-FTP/NASD/CMU-CS-97-118.abstract.html "Filesystems for network-attached secure disks"]. Garth Gibson, David F. Nagle*, Khali Amiri*, Fay W. Chang, Howard Gobioff, Erik Riedel*, David Rochberg, and Jim Zelenka, Technical Report CMU-CS-97-118, July 1997. * [http://portal.acm.org/citation.cfm?id=258696&coll=portal&dl=ACM "File server scaling with network-attached secure disks"]. ''Joint international conference on measurement and modeling of computer systems'', Seattle, Washington, United States, 1997, pp. 272β284 {{ISBN|0-89791-909-2}}. == External links == * {{Commons category inline}} {{Data storage}} {{Authority control}} [[Category:Network-attached storage| ]] [[Category:Server appliance]] [[Category:Software appliances]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Authority control
(
edit
)
Template:Citation needed
(
edit
)
Template:Cite book
(
edit
)
Template:Cite journal
(
edit
)
Template:Cite magazine
(
edit
)
Template:Cite press release
(
edit
)
Template:Cite web
(
edit
)
Template:Commons category inline
(
edit
)
Template:Data storage
(
edit
)
Template:Div col
(
edit
)
Template:Div col end
(
edit
)
Template:ISBN
(
edit
)
Template:Main
(
edit
)
Template:Mono
(
edit
)
Template:More citations needed
(
edit
)
Template:Redirect-distinguish
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)
Template:Snd
(
edit
)
Template:Spaced ndash
(
edit
)
Template:When
(
edit
)