Don't know if you are still looking at this or not, but here is my suggestion:
Continue using RoboCopy and keep your library as the master. Setup a second library at the remote site, and use RoboCopy to bring the data back, and then use the Library Services on the local copy, then RoboCopy to sync them again. I know that's a lot of work, but keeps things from getting messed up by writing over each other. Plus RoboCopy is a very good program for moving and syncing the data.
Sorry, but can't help you with Windows Server DFS Replication.
Thanks David, that is pretty much what I came up with if we end up adding the new location. For now, that has been put on hold so I have time to look for other solutions.
I just read this discussion and I am just now going through this same issue. Mentor is recommending I use DMS but I'm hoping for something simpler and free. Can you tell me has anything changed with your approach since 2009? Did you come up with a better solution or is it the same as what David_S suggested?
I am still using the RoboCopy method to transfer the libraries. We are currently only doing library management at one location, so that simplfies things a lot