Thanks for the comment.
I'm a sysadmin albeit only recently changed into this role.
FreeNAS was my first choice when I thought about building this solution, however, instinctively, it feels over engineered for my needs.
Sure, if I want a NAS with GUI, Jails and running VMs etc, I'll run to FreeNAS.
But, I'd like a minimal core (FreeBSD + ZFS + NFS + rsync) which lowers the failure surface. I will write a few scripts to keep an eye on the health of the server, and that'll be it.
Good to know that your NAS survived a 2/5 disk failure.
While I would personally prefer FreeNAS (or just to roll my own), remember that you're supposed to be planning for the next person in your position. Sometimes a commercial appliance really is the best way to go. If you do roll your own or set up FreeNAS you need to build lots of docs and make sure they're stored somewhere the next guy will find them.
Ultimately it depends on the company, it's just a compromise I have had to make before so I thought it worth mentioning.
Good point. I'm thinking of this custom solution only because of the simplicity of this requirement(NFS backup). I'm planning to prepare a thorough documentation of what I did to build this solution and how to maintain it.
- IMO, having owned a couple readynas(es) in the past, FreeNAS is a good compromise between ease of setup and functionality. To me, it does not feel over-engineered. In fact, it feels like it gives you enough to do everyday stuff easily through the UI, and drop into ssh if necessary. I've only had to do this a few times. To wit: I would take a stock FreeNAS over manual setup anyday.
- The 2 disk failures I've experienced were independent of each other. I have not experienced a simultaneous failure of 2 drives. I have preventative measures in place, namely in the form of a hot-spare for the pool and an aggressive resilver schedule that runs weekly.
Good to know that your NAS survived a 2/5 disk failure.