Current Recommendations For a Home File Server? 170
j.sanchez1 writes "The recent coverage of Shuttle's new KPC has gotten me thinking (again) about a small, low-cost headless file server for home. In the past, I have looked at the iPaq and considered using older computers I have lying around, but for various reasons I have never jumped in to do it. Do you guys have any suggestions on what to use for a home file server (hardware and software)? The server would be feeding files to Windows PCs and connected to the network through a Linksys WRT54GL running DD-WRT firmware."
There are a host of good options these days; what has the best bang for the home-user's buck?
Why not get a NAS? (Score:2, Insightful)
It's not ultracheap (~$500-$600 + HDD cost) but have low power usage compare to any full PCs
DLINK DNS-323 (Score:3, Insightful)
DLINK DNS-323
Two SATA bays. Can slide in the drives w/o tools.
Print server (USB)
Can run in RAID0, RAID1, or JBOD (I chose RAID1).
web interface for config.
I bought two 512Gb WD drives which were on sale for $119 each.
Some peculiar behavior if you really want a secure system: passwords couldn't include non-alpha chars!? And it didn't allow spaces in the WORKGROUP name for the samba mount, which isn't an MS requirement.
But for home use where you're already considered secure and not so worried about multiple users, I find it great having one giant
The reviews on Amazon are love/hate, I think for the above reasons. Probably not be the best set-up for an office or in The Wild.
Random review here: http://www.techworld.com/storage/reviews/index.cfm?reviewid=469 [techworld.com]
Easy (Score:2, Insightful)
1. RAM (make all of it fit in RAM; most expensive; ridiculously fast; will probably require a 64 bit machine). Hint: Google uses pulls the critical stuff off RAM, not hard drives.
2. Flash storage (excellent for concurrency; fragmentation and parallel operations don't degrade performance; lots of other advantages such as durability, power, noise, size, weight, can be turned off anytime, etc.).
3. Hard disk drive. Disregard the bus, the hard disk is usually slower anyways. Especially skip SCSI unless you have a very good reason for it; prefer SATA.
And there you go.
Learn from my mistakes - Keep your data safe (Score:2, Insightful)
1. Ventilation - You don't want your hard drives getting hot and crispy. Hard drives tend to break more often when you leave them cooking themselves for a couple of months.
2. CPU - Software RAID (especially writing to RAID 5) is very CPU intensive. Ideally you'd have a hardware RAID controller, but they're too expensive. Your better off getting a decent CPU that can handle all of the RAID goodness and everything else the server does. I'd recommend either a dual core or hyper threading.
3. Logs - Make sure whatever setup you have emails you, beeps at you, or does something to let you know if one of your drives fails. A 4 disk RAID 5 is worthless if more than one drive fails. If you're really serious about keeping your data, don't limp on with a missing drive on your array.
Re:Windows Home Server (Score:3, Insightful)
However according to the FAQ's on MS's own website;
We want to help ensure customers have a simplified, quality experience with Windows Home Server. The best way to do this is to deliver Windows Home Server on integrated hardware/software solutions through OEMs and system builders that are tested and meet system requirements.
Personally I would say that if you are running (or planning to run) Vista *and* have a requirement for the features provided *and* are not too interested in flexibility *and* have the budget for it, then this is probably a nice and simple approach. For anyone else there are lots and lots of options that (with various degrees of work) will do the same or more for less.
Home server. (Score:2, Insightful)