What Is A Home Computer Server?
Some people are confused (or just have the wrong idea) about what a computer server actually is.
The technical definition is that a server is a computer dedicated to providing a specific service or services.
Concerning what you would use in the home, the most common example is a file server, i.e. a computer where its sole purpose in life is to store files you can upload or download at any time on your home network.
What qualifies as a home file server?
It can be any computer. It does not have to be some refrigerator-sized monster box.
Why would you use a file server in the home?
Because if you have gigs and gigs (possibly terabytes) of files it’s better to store that on a computer that’s not your primary system so your OS runs smoother. (The less your hard drive gets “beat up” the better.)
Example use: If you do a lot of DVR, having a file server would definitely serve to your advantage.
Does an external hard drive count as a file server?
No, because it’s not a computer. A server technically has to be a computer with an OS on it.
What’s the best file server setup?
Although this could be put up for debate, the best setup is usually a Linux distro with no GUI whatsoever. The box is completely administered remotely (as in over the network via telnet session from your primary computer) and the box itself only has two cables plugged into it, that being the power cable and a network cable. In this setup the OS uses the least memory possible to deliver maximum performance.
Aside from the speed, the file system it uses (ext2 or ext3) is better suited than Windows NTFS for server-specific stuff. Never do you have to worry about “defragging” the drive with a Linux partition because you simply don’t have to.
What if you wanted to use Windows instead?
If you don’t feel like using Linux you can use any Windows OS as long as its an NT-based Windows like Windows NT 4.0, 2000, XP or Vista with an NTFS partition. If you use FAT32 the inherent problem is that you won’t be able to store any files over 4GB in size because that type of partition won’t allow it, so never use FAT32 in a home server setup because yes, you inevitably run into the 4GB filesize limit problem.
The Windows you use on a file server should be stripped down as much as possible. Disable every service that’s not necessary, such as Themes, Error Reporting and so on because it’s simply not required. Don’t run a screen saver, don’t use any wallpaper, etc.
What are the most important components of a home file server?
The hard drives and the network card, in that order.
Don’t put cheap hard drives in a home file server. Spend some cash and get decent ones.
PATA or SATA drives? The answer here might surprise you, but the answer is PATA. Why? Because generally speaking PATA drives consume less power. Since this is a box that’s just going to sit there most of the time, you want it to consume the least electricity possible.
Your router is most likely 100-megabit enabled. Use a network card that takes full advantage of this.
Should your home file server be wireless?
If you have the choice, no. It should be “hard wired” to the router. Makes for better file transfers and far less chance of data going corrupt – not to mention the transfer speed is much faster (assuming the other computers connected are also hard wired).
Does the router count?
Absolutely it does. If you find that when transferring large files you have a “hard time” completing the transfer (or it never completes) even when wired, you need to get a better router.
The best routers are usually Cisco – but they cost a bit of money. Linksys and D-Link are also very good choices for the home as well.
Tip: If you have a decent router but are still having problems, replace the network cable. 99% of all wired LAN problems start (and usually end) with cabling.
Does the file server have to be a super-fast computer box?
No. All it needs to do is be able to support the hard drives and 100mbit card you put into it. You could get away with something as slow as a Pentium II 233MHz – but in that case you’d absolutely have to used a no-GUI Linux because a NT-based Windows would slow it down to a crawl in short order.
Did I miss anything? Got a suggestion?
Feel free to chime in with a comment or two.