I need a file server/backup system.
Am just not sure if to go FreeNAS or Windows Server 2016 using parity storage.
I know technically, FreeNAS is not a "file server" but for the most part, it would do what I need it to.
Multiple users/systems in the house, I want to give each use their own "home" area for storage and offload personal storage to a server to free up space on clients with the ability of somehow running a system image for each system once every week or so with minimal user intervention so if anything borks, reinstall image, job done (Saying that, I am not expecting FreeNAS or Windows Server to do that, if it did, even better).
I would generally say (excluding the automated backup part) FreeNAS would suffice but I really want to have a play with active directory stuff so now would be a good time to fix that up. The AD stuff is just a personal jolly, not a specific requirement but I would like to setup roaming profiles for users in the house.
My thoughts are, two options.
1.
FreeNAS build for now then add a seperate Windows 2016 server down the line for the AD stuff.
2.
Go for a Windows server 2016 build out the gate and let that run everything. I assume this will need a beefier system than a standalone FreeNAS build?
Would a seperate Freenas box and then a Windows server box play nice? I assume it would but generally, is it is considered "good practice" to have your storage pool and file server in the same box so to speak or does it not really matter?
If a Windows Server box is doing none of the "heavy lifting" so to speak if just using for backups commands, AD etc, is it resource hungry?
Hope this makes sense, if not, apologies
Am just not sure if to go FreeNAS or Windows Server 2016 using parity storage.
I know technically, FreeNAS is not a "file server" but for the most part, it would do what I need it to.
Multiple users/systems in the house, I want to give each use their own "home" area for storage and offload personal storage to a server to free up space on clients with the ability of somehow running a system image for each system once every week or so with minimal user intervention so if anything borks, reinstall image, job done (Saying that, I am not expecting FreeNAS or Windows Server to do that, if it did, even better).
I would generally say (excluding the automated backup part) FreeNAS would suffice but I really want to have a play with active directory stuff so now would be a good time to fix that up. The AD stuff is just a personal jolly, not a specific requirement but I would like to setup roaming profiles for users in the house.
My thoughts are, two options.
1.
FreeNAS build for now then add a seperate Windows 2016 server down the line for the AD stuff.
2.
Go for a Windows server 2016 build out the gate and let that run everything. I assume this will need a beefier system than a standalone FreeNAS build?
Would a seperate Freenas box and then a Windows server box play nice? I assume it would but generally, is it is considered "good practice" to have your storage pool and file server in the same box so to speak or does it not really matter?
If a Windows Server box is doing none of the "heavy lifting" so to speak if just using for backups commands, AD etc, is it resource hungry?
Hope this makes sense, if not, apologies