Over the past few years, I have on more than one occasion had nothing but trouble when trying to replicate File Data from one location to another. This is usually especially true if there is a considerable amount of File Data. I have in some instances seen that the DFS process can take several weeks to copy File Data from one Server to another, even if they are in the same Active Directory site. I have also attempted to seed the data with Robocopy first, and then turn on DFS replication but then DFS would again take weeks to sync the DFS data between the two File Servers.
I have read over the past 6 months that it was possible to export a copy of the DFS database after seeding the data via Robocopy, and thus negating the need for DFS to compare all the data and getting the two File Servers to be in sync. I was a little apprehensive and a little put off by the process, but after reading this blog: https://windorks.wordpress.com/2014/08/13/dfs-r-walkthrough it sure sounded simple enough. I looked at the process on the blog and then read the Microsoft post on the process, and gave it a shot… I am seriously impressed! After seeding some large test data via Robocopy, setting up a base DFS replication config and then exporting the DFS database out it was all in sync and ready to go. I urge anyone that wants to use DFS to seriously look at this method, and it is certainly one that I am going to be considering to use for any future DFS based replications or migrations.
Here is the link again: https://windorks.wordpress.com/2014/08/13/dfs-r-walkthrough
Thanks to the blog owners – I owe you a beer I think :D.