HeloJunkie
Patron
- Joined
- Oct 15, 2014
- Messages
- 300
OK so my hobby system is running 3 x 6 Drive vdevs (4TB drives), soon adding a 4th vdev using 8TB drives (as soon as the drives arrive) all running RAIDZ2. While this is my 'hobby' system, it would sure stink to lose all the media I have stored on my system due to anything, so I have decided to look at firing up a second FreeNas box to backup my primary FreeNAS server.
I know the 'purest' answers to my questions are to build the second server the same as I did my first (see configs below in my signature) using best practices, but my goal is a less costly, mostly offline backup. I want to fire up my backup FreeNAS system about once a week, do an rsync between systems and then shut back down. If I lose the pool on my primary, I can fix the glitch and restore from the backup FreeNAS server. The backup FreeNAS server will never be used to serve data to anyone or anything other then to restore my primary machine.
My primary machine talks via NFS to a single machine - a plex media server. No other shares or mount points are used.
So....I understand best practices and know them well, but since this is a BACKUP system only, I was wondering about the following:
1) Do I have to keep to the 20% available overhead rule to keep ZFS happy or can I use 5 to 10% instead for space savings
2) Can I get by with 32GB RAM as opposed to 64GB or 128GB calculated via best practices.
What I DON'T want is a crippled system as a result of trying to save a few $$$ on a backup solution, but at the same time this is not a production system so can FreeNAS run with less ram and less overhead drive space if it is not being used as a primary system.
Thanks for any insight!
I know the 'purest' answers to my questions are to build the second server the same as I did my first (see configs below in my signature) using best practices, but my goal is a less costly, mostly offline backup. I want to fire up my backup FreeNAS system about once a week, do an rsync between systems and then shut back down. If I lose the pool on my primary, I can fix the glitch and restore from the backup FreeNAS server. The backup FreeNAS server will never be used to serve data to anyone or anything other then to restore my primary machine.
My primary machine talks via NFS to a single machine - a plex media server. No other shares or mount points are used.
So....I understand best practices and know them well, but since this is a BACKUP system only, I was wondering about the following:
1) Do I have to keep to the 20% available overhead rule to keep ZFS happy or can I use 5 to 10% instead for space savings
2) Can I get by with 32GB RAM as opposed to 64GB or 128GB calculated via best practices.
What I DON'T want is a crippled system as a result of trying to save a few $$$ on a backup solution, but at the same time this is not a production system so can FreeNAS run with less ram and less overhead drive space if it is not being used as a primary system.
Thanks for any insight!