It's the 'ours' box in my sig. I'm leaning heavily towards Win 2016 Datacenter and Hyper-V rather than ESXi, simply because I have a free license and already know VMware well enough. The system will be for data duplication/backup from our other systems, as well as running Blue Iris and providing IP services to my camera network. I'm hoping to have one port of the Intel NIC connected to the PoE switch, and the other port going to my router. The idea is that you wouldn't be able to access the cameras directly from the main home network, only through the web portal presented by Blue Iris. I think I want to use the Server 2016 Web Application proxy with an outside port on the router NATted over to that sytem.. I think? Definitely not looking to set up a whole VPN, I know that much.

I think I'm going to let Windows manage the drives with a double parity setup. I think. I was originally going to use Nas4Free, but after reading good things about REFSv2, I figure why not give it a shot? I plan on letting the top level/host Windows install manage the storage, making new virtual disks for VM use as needed, setting up the actual VMs on the 960 Evo. As present, I'll just have one guest OS install, for Blue Iris. The data duplication/backup services, I'm not sure. Set up an iSCSI target? Use Windows shares? I'm really not sure which way to go on this. I want to set it up so that my other PCs can send data backups and incremental backups to the server, but cannot wipe or overwrite them after they are sent - in case of malware, of course.

We use mostly Ubuntu systems at work, so I have almost no Windows server experience. If it sounds like I'm clueless, it's because I am actually clueless. I'd really appreciate any pointers on configuring the server, accounts, best practices, security, NIC config, DHCP (I think I want the server to provide DHCP for stuff on the PoE switch and also to route between the two ports on the NIC if that's something Windows can do), and anything else I've forgotten to mention. I would like to leverage Windows Server 2016 as much as I can, since I'm doing this as much for the learning experience as for anything else, so kindly refrain from suggestions along the lines of 'use linux instead.'

I greatly appreciate any input