What is a file server?

Essentially, a file server is a computer that stores files, is attached to a network, and provides shared access of those files to multiple workstation computers.  File servers do not perform computational tasks - that is, they do not run programs for client machines.  Furthermore, they do not provide dynamic content like a web server.  Still further, file servers are not like database servers in that the former do not provide access to a shared database whereas the latter do.  File servers provide access to static files via a local intranet through Windows or Unix protocols as well as over the internet through file transfer or hypertext transfer protocols (FTP and HTTP). 

What can you do with a file server?

The primary function of a file server is storage.  For the home user, one central storage location can increase overall computing efficiency and reduce overall computing cost.  By placing all of your important files in a single location, you do not need to worry about different versions of files you're actively working on, wasting disk space by having multiple copies of less-than-important files scattered on different systems, backing up the right files onto the right backup storage medium from the right computer, making sure every PC in your home has access to the appropriate files, and so on. 

From a system builder's perspective, a file server can also liberate your various workstation computers from having to accommodate multiple hard drives, and decrease overall hard drive expenditures.  With the rise of SSDs, which offer tremendous performance at a high cost per GB, a file server can free workstations from the performance shackles of platter-based disks - an especially useful consideration for laptops and netbooks, where the small capacity of an SSD is often a deal breaker since these mobile computers usually can house only one drive.

A dedicated file server allows every user in a home - whether they're at home or on the road - to access every file they might need, regardless of which particular device they might be using at any given time.  Dedicated file servers also allow you to share your files with friends and coworkers - simply provide them with a URL, a login name and password, and specify what content they can access.  For example, maybe you'd like to share your kids' camp photos with the in-laws - but your cloud storage capacity won't fit all of those photos plus all of the other stuff you have stored in your cloud drive locker.  Maybe you'd like to share sensitive information with a colleague that you'd rather not upload to a server owned by Amazon or some other third party, but the files are too big to email.  Or maybe you'd simply like to access your 200GB library of MP3s while you're holed up in a hotel on business with nothing but your 60GB SSD-based netbook.  These few examples are really only the tip of the iceberg when it comes to the utility of a file server. 

That said, there are alternatives to a file server for all of these needs.  You could dump all of your photos onto a flash drive and give them to the in-laws the next time you see them - but you have to do this every time you want to share more photos - and who knows if you'll get your flash drives back?  You could mail a DVD-R to your colleague - but perhaps a DVD-R's ~4GB capacity is insufficient, and snail mail takes days if not weeks to be delivered.  If you're on the road, you could just bring along your portable external hard drive - which takes up space, and can be lost or stolen.  A file server is a simple, singular solution to all of these problems.  Home file servers do not require enterprise-grade hardware and can be very affordable.  They can also be made from power-sipping components that won't spike your electrical bill.

What considerations are important in building a file server?

Because the primary role of a file server is storage, this is the most important aspect to think about.  How much storage space do you need?  Do you want to share 50GB of photos taken on a point and shoot digital camera?  500GB of music?  2TB of movie DVD ISOs?  30TB of mixed media and work-related files?  Also, at what rate are your storage demands growing, and how easily do you want to be able to expand your file server?

How easily do you want to be able to administer your files?  Many of the more powerful file server operating systems are unfortunately not particularly easy to run for the non-IT professional.  However, there are file server OS's that are easy to run.  What about being able to recover your files in the event of catastrophe?  Placing your files in one computer is tantamount to putting all of your eggs in one basket, which can be risky.  What about security?  Anything on any sort of network is vulnerable to intrusion.  While this guide answers all of these questions, it is aimed at home users and therefore necessarily makes some sacrifices to storage space, administration capabilities, recoverability, and security - simply because home users typically can neither afford nor require professional-grade file server solutions.

Why build a file server instead of using NAS?

Simply put, a NAS (networked attached storage) device is a computer appliance.  It is built specifically to provide network-accessible storage.  NAS devices typically offer easier administration than file servers (some are a few mouse clicks away from plug and play operability), but are often limited by proprietary software, and are neither as capacious nor as expandable as a dedicated file server.  Further, higher-end NAS devices that can house as many hard drives as some of the builds outlined in this guide are more expensive than the file server alternative.  Finally, because they are designed with only one purpose in mind, they are not as flexible as a file server, which in a multi-system home, might need to be co-opted into a basic workstation at a later point in time.  That said, while NAS devices are outside the scope of this guide, they're worth investigating if you're not already familiar with them. 

This guide is laid out differently than my previous builder's guides in that rather than detailing specific systems at specific price points capable of performing specific tasks, it instead discusses options for operating systems and types of components and how these different options are best suited to addressing different needs.  That is, maybe you need a lot of storage space but you're not particularly concerned about backups.  Or perhaps you don't need much storage space at all but want to use a very straightforward file server operating system.  By mixing and matching recommendations to suit your needs, hopefully you'll be able to construct a file server with which you'll be pleased!

File Server Operating Systems
POST A COMMENT

152 Comments

View All Comments

  • HMTK - Monday, September 5, 2011 - link

    I've got one and it happily runs Windows Server 2008 R2, even as a domain controller and Microsoft Security Essentials for AV. Only 1 GB RAM but that's enough for simple file storage. I still have 2 bays free if I need more than the 2 TB mirror I have now. And it has an eSATA port I think. Reply
  • tmensonides - Monday, September 5, 2011 - link

    I have a readynas atom as a file server, but have been toying with building an atom based system as 1: A backup for the readynas and 2: a webserver for my wifes business blog (photography)....her blogsite maybe gets 50-75 hits and a max/good day.....

    Could an atom bases syatem handle that with out super crappy load times?
    Reply
  • bobbozzo - Wednesday, September 7, 2011 - link

    If you're using wordpress, it can be pretty slow on low-end hardware, but 75 hits is nothing. Reply
  • HMTK - Monday, September 5, 2011 - link

    Who's going to have a 10 Gb switch at home? Please get real. Most SMB's don't even have that. Why not go full 8 Gb fiber while you're at it :-) Reply
  • alpha754293 - Tuesday, September 6, 2011 - link

    @HMTK

    12x IB EDR FTW!!!!

    (what's up? long time no talk.)
    Reply
  • futurepastnow - Monday, September 5, 2011 - link

    I'm just going to post the specs of the file server I built a little over a year ago:

    Windows Home Server (original edition)
    Athlon LE-1660 45W processor
    2GB DDR2 RAM
    Gigabyte 740G mATX mobo
    Six WD Greenpower 1TB drives
    Antec Sonata case
    Corsair 400CX PSU

    I originally tried to build a lower power WHS box with an Atom processor, using a PCIe card to add more SATA ports so I could run all six drives. Performance was not satisfactory, drive indexing and balancing took way too long, and (because of the PCIe card) I got no warning that one of the drives was filling up with bad sectors before it died. And due to the slowness of the Atom, not all of my 2+TB of data had yet been duplicated across the six drives.

    I replaced it with a very cheap K8 CPU and the cheapest motherboard that had six SATA ports built-in and was from a brand I trust. The Athlon is much faster, although a lower-clocked dual-core would have been better. There are better options for those building today, anyway. I'm still very happy with the server in its current form.
    Reply
  • Malih - Monday, September 5, 2011 - link

    What about underclocking+undervolting the overheated but cheaper Athlon CPU, that would make it quite power efficient and lower in temps compared with the Pentiums in that regard.
    I'm hoping some tweaking tips like this in a Builder's Guide article from Anandtech.
    Reply
  • GTaudiophile - Monday, September 5, 2011 - link

    In the OS section of the article, he writes:

    "While there is an Ubuntu Server Edition, one of the easiest ways to turn Ubuntu into a home file server is to install and use Samba. (Samba can be used on not only Ubuntu, but also FreeBSD.)"

    I am confused by this a little bit.

    SAMBA is by no means exclusive to Ubuntu or any other distro. In fact, I use SAMBA shares through FreeNAS and it works quite well. I just think the article alludes (to the lay-person) that SAMBA is somehow exclusive to Ubuntu and it is not.

    Secondly, why does the article not touch on NFS at all? From what I understand, NFS is faster and more reliable than SAMBA.
    Reply
  • Braumin - Tuesday, September 6, 2011 - link

    For the average person, WHS 2011 is just the easiest way to go. If someone is moving up from a NAS, then they don't just want file storage. WHS offers great and pain free PC backups with image based restores, a great remote access page with full SSL, and it is dead easy to configure and use.

    I think the comments have gotten a bit out of hand with various RAID incarnations that people have. Most people don't need RAID. They need centralized file storage, and then need a backup. WHS does both. It also supports RAID if you really need it.

    I have to say, I would rather see a bit more in depth on this topic. It is important for many people these days since everyone seems to have at least two computers per house, if not more.
    Reply
  • semo - Tuesday, September 6, 2011 - link

    I think that an article of such nature should go in a lot more depth in regards to backups (strategies, equipment and best practices). Reply

Log in

Don't have an account? Sign up now