Comment Storage Spaces + Crashplan (Score 1) 366
I have been using storage spaces on a Windows 2012 R2 server for 3+ years now and it's been fine. I have 6 x 3TB drives in a parity storage space using REFS (not NTFS) and run a SMART monitoring ("WindowsSmart") program that emails me every day. I have no idea why this functionality wouldn't be built into the server. Twice it's reported questionable health (one time was CRC errors due to a bad cable, the other time, the drive was accumulating errors); I replaced the drive and the array rebuilt quickly. This is software, not hardware raid, of course, and it does sometimes pause when copying lots of new data.
The most important data (documents, family photos and videos) are backed up to CrashPlan. I'm currently pushing 5TB there. I have it set to throttle uploads to 5mb/sec (I have TimeWarner-now-Charter's '200mb down/20mb up plan without caps) and, while I can't say how long it took to initially synchronize, it keeps up nicely now. I back up raw VHS family video captures, which are 14GB/hour so the originals are always available.
The data that's not backed up onto Crashplan is backed up onto a local QNAP 8-disk NAS that I was able to pick up for a great price. I stick old drives into it and use RSYNC to manually duplicate the remaining data across the QNAP's varied 1.5 and 2TB drives. If one of them croaks (and it happened once), I just replace it and hope the Windows 2012 server doesn't croak until the data is copied again.
But all the stuff I wouldn't want to lose in a fire is in Crashplan. It's very inexpensive in the US (something like $60/year for unlimited backup storage) and kind of a no-brainer for anyone with the upload bandwidth and no cap. And yes, I have recovered some accidentally deleted files, although I can't swear they're all available.
The only thing I'd do differently is use NAS drives in the server instead of cheaper desktop drives. The prices are much closer now than they were back in 2013. I noticed when the one drive was failing that copies to the server would pause for 30 seconds at a time, but the array never dropped offline. Presumably NAS drives wouldn't exhibit this problem.