So, quick question to the Windows networking and storage experts. I need a way to have 2 servers offer the same UNC path to network clients. So that if one of them goes down, the other one takes over. To achieve the "cluster" connectivity itself to point UNC to either server I simply use DNS Round Robin technique and programmed a small tasktray agent that runs ipconfig /flushdns on the clients if one of the two servers cannot be pinged, as a sign that it's time to change. This works fine as the domain updates immediately to correct server IP that's still up - back and forwards. Tested OK. The UNC then points to the other server that's up. What I haven't figured out, is how to synchronize/replicate the shared folders between them properly. I want each server to be a full backup of the other, ready to take over automatically if the other goes down. And I only have 2 physical servers to set it up with. Currently there's a VM with the shared folder using Hyper-V replication from one to the other using workgroup SSL, but this requires manual failover once one of them goes down. I need automatic cluster-like/load-balancing behavior so the users still have service without waiting for tech support if a server goes down. What I've been reading about windows networking, it seems nothing will offer exactly what I'm thinking of without going shared storage (SAN/NAS). DSF-R (distributed file system replication) will seemingly crash if a member goes down, and it requires AD as well which I have no experience with but will set up if it helps. I simply need a replicated shared folder to be available on arbitrary server that's still up, if one goes down. And if it comes up again, I need them to synchronize/replicate eachother before the share becomes available again. < This is the main part I haven't figured out yet. I've been thinking about pausing lanmanserver while it syncs with robocopy or some other program, but figuring out exactly when to do it and how to trigger it is messy. Is the only way a shared RAID/SAN/NAS storage server/unit? Or is there really a way to keep 2 servers fully replicate a simple shared folder where clients always work with the newest files, regardless which server they connect to. Using a SAN/NAS shared storage just makes that storage another single point of failure again, so trying to figure something out using just 2 physical, identical servers. Or, could I set up both servers as a storage cluster for eachother somehow? They're running 2012 R2. The strict limitation I have is the 2 physical servers with 2012 R2 on each. I just wanna make the most out of them. As automatic as possible. Maybe it's simply impossible. As if host1 goes down, host2 takes over for a while. Host1 comes back, but if Host2 then is down, Host1 only has old files as it can't sync back updates. Halting both servers. This is an unavoidable potential MURPHY problem if I'm going to do it this way, right? Best to go NAS/SAN for storage regardless perhaps? Thanks.