How to organize a fault-tolerant file server?

Question

Hyper-V

Greetings!
There are 2 servers running Windows Server 2012r2. On both, the role of Hyper-V is raised, plus one of them acts as a fairly large file server (6TB, daily growth of 20-40GB).
It is necessary to provide fault tolerance for the file server (so that in the event of a failure of the first server, users can access files with minimal downtime).
It would be storage - the issue would be beautifully resolved using Scale-out, but it is not :(
The option with Hyper-v replica comes to mind, but the idea of ​​virtualizing a 6TB file server in itself raises some doubts.
Are there any alternative scenarios, allowing to organize fault tolerance of a file server in the automatic/semi-automatic mode?
PS By itself on the second server there is a place under a file server.
PPS The option with DFS was considered, but was rejected due to extreme gluttony in terms of disk space.

Answer 1

Starwind Virtual SAN
Licensed in your case in 2 types:
- 2 servers and 4TB storage - 144,000 rubles.
- 2 servers and anlim Tb - 577,000 rubles.
And, surprising at first glance, it is cheaper than vmware vsan, cheaper than storage in windows 2016. Fault-tolerant hardware storage (2 active-active controllers, two hba controllers for servers) already depends on the number and types of disks, but it is easy will pass for 577 000.
Can reconsider volumes of fault tolerance? Part of the data just to keep as is?
And then Starwind for 144 is not so expensive? ..
The rest is not for windows. There seems to be something there, either on KVM, or something else, and even without money. But this requires a different experience.