I have just set up DFS in our environment. We made a full backup of our existing file server running 2003r2, restored the backup to our new 2012 server and then set all of the shares as individual replicated folder sets between the 2 servers to make sure all changes get replicated. All users were still pointed to the 2003r2 server, until today when we pointed some users to the namespace as a test, and that really pointed out some issues.
One logs folder that is being replicated has a very large discrepancy, in that the original 2003r2 server has over 10,000 files in it, and the corresponding folder on the 2012 server contains less than 5,000 files. Then we also noticed that one log file that gets written to multiple times throughout the day exists on both servers, but has completely different data in both servers - almost as if it is alternating which file to write to instead of writing the file and replicating the change as we would expect.
There are no errors showing in the DFS replication log in event viewer. I ran a health check, and for the 2003r2 server, for each replicated folder, it says the status is normal, the backlogged sending transactions and backlogged receiving transactions are both just listed as "--". The # of files received is 0. On the 2012 server, each replicated folder says the status is Indeterminite. The staging folders seem to be empty as well.
During our initial testing, the replication appeared to be working as we expected it to work... I could create a file in the namespace, and it would almost immediately make the change on the server. Now this is not happening, but the services are running and DFS itself seems to think it is running just fine.
Does anyone have any ideas that would help me figure out how to get this working?