From reading the DFS documentation, AD appears required.
This is a problem for us because our servers are either stand alone (not in AD), or part of our hosting service AD, and AD is out of our hands.
The question is: How to do DFS, or something like DFS, when the servers are:
- In different DCs , and
- Not in any useful AD
Machines are Win2012-R2 and/or Server 2016
Looking to automagically mirror tlog backups and sql backups across machines, on a close-to-the-minute basis.
DFS is usable but a) cause issues working with open files b) Hyper-V, SQL Server and Exchange has no DFS support c) can't avoid a spit-bran issue. When multiple users works with the same file that has no sync between hosts will cause a two different original files.
For the case I asume the build of HA shared storage between servers will do the job. However, iSCSI storage vendors such as S2D, HPE VSA or StarWind Virtual SAN can provide required storage replication but all require the implementation of AD. Consider go with Active Directory to benefit with configuration of SMB/NFS on top of shared "nothing" storage.
DFS-R requires active directory, so that option will not be available to you. As yagmoth mentions in his comment, you could use robocopy
For example:
robocopy /mir /mot:10would run a mirror every 10 minutes. Could set it as a task on startup, etc..Beyond that, there are 3rd party utilities that could also perform similar functionality - including backup dedicated utilities.
There are two options that I have used and work relatively well.
Peersync - http://www.peersoftware.com/products/sync-backup/peersync-for-servers.html
Is licensed however works really well, very well documented and easy to understand.
Freefilesync - http://www.freefilesync.org/
Is free only downsize there is no inherited automation, but once you configure your two directories to be synced, it has the option to create a batch file that can be run though a schedules task.