Storage Spaces Direct picks up the baton from Microsoft Clustered Storage Spaces, meaning it is a true SDS technology for Windows Server 2016. The testing of S2D is in full swing right now, and in this research, we provide a systematic guide on a practical deployment of a fault-tolerant 4-node setup.
Enterprises seek for ultimate performance, total fault-tolerance and availability to secure their business continuity. Thus, the 4-node setup which ensures exceptional uptime even in the case of multiple node failures seems to be the right choice.
The setup consists of 9 detailed steps: from Windows Server roles and features installation to the node failure test executed with our own specialized tool called Storage Data Corruption Test.
In the result, we have successfully built an S2D 4-node setup, which can withstand a node crash. It proves to be a good example of Enterprise-level infrastructure ensuring high uptime and performance due to overprovisioning in hardware resources.
Read the full article here: https://www.starwindsoftware.com/blog/microsoft-storage-spaces-direct-4-node-setup-2 to learn more about the setup process and detailed failover check results.
Development of any technology requires ideas, which need a lot of testing, before then can actually work. The problem is that testing and POC typically happen before the idea can make any money, relying heavily on free and open-source solutions.
There is no decent free SMB3 fileserver. Those available are critically unreliable or just aren’t working properly. In case you need one right now and there is no other way of acquiring it, there is a way – the Free Microsoft Hyper-V Server 2012R2. However this method violates license agreement, so it’s not in any way a permanent solution for your problems. You may take the risk and try it once in order to see if your idea works, but we still strongly discourage you from repeating this experiment.
In any case, let’s see if you can build an SMB3 fileserver on Free Microsoft Hyper-V Server 2012R2 and if it works, go further and see if we can create a failover fileserver. Check out the following posts and see:
Hyper-V: Free SMB3 File Server
Hyper-V: Free “Shared Nothing” SMB3 Failover File Server