What solution should be used in this case to build a file server?

Question

Microsoft

It is necessary to make file storage for backups, production data and roaming profiles with redirected folders of users from the terminal server farm, WSUS data, WDS. High performance is not required, so no disk shelves are planned. The entire server infrastructure is based on several hyper-v hosts, it would be nice to include file servers in it.
What do you want:

• Disaster recovery (if one node fails, the second must contain an exact copy, with all NTFS permissions and so on)
  
• Solution scalability
  

To put it briefly, it would be desirable sort of RAID 1 from file servers. At first, it was planned to deploy DFS from several nodes for these needs, but for roaming user profiles, this solution is not the best idea. I am not familiar with file clusters, but if I understand correctly, it implies a single storage for several nodes - we do not need this.
What other options are there?

Answer 1

I'm not sure what will work, but look towards DFS
Another option is to look at the solution from Starwind

Answer 2

DFS replication will allow you to have a copy. The relevance will depend on the amount of data being written and the speed of exchange between DFS servers.
The best you can do with DFS is one active server and any number of cold standby servers.
You can organize data access through dfs namespaces or use a common alias in dns. In the event of an accident, you change the record, and the clients, not noticing anything, will already be working with the backup server.
I don't know anything better. The main problem is in controlling the simultaneous writing of one file on different servers. There are no blockings. The newer one will overwrite itself on both servers.