We have a network containing four fileservers on four different locations.
These file server were running 2008 R2 and DFS-R was working fine in a full-mesh configuration for several replication groups. As diskspace became an issue and the deduplication test showed us lots of diskspace could be reclaimed by switching to Server 2012 and implement deduplication, we started a project to upgrade al file server to Server 2012.
We started with our main file server and simply created folders, pre-seeded these folders and added the folders to the existing DFS-R replication groups. No problems thus far.
After a few weeks of migrating and testing we disabled all 2008 R2 servers and Server 2012 became the production platform.
Now we have a very strange issue.
Without errors logged in the DFS Replication log, one of the servers doesn't send updates to the other servers anymore for only replication groups located on a specific drive (f:). Other replication groups on other drives don't show any problems. Replication for the problematic replication groups on the other servers keeps working just fine.
The data on drive F: contains application folders containing network installation folders of applications. Some also contain application data, but this is rather static. Nu huge amount of changes are created. Also our AppV application share is located on this drive.
Sometimes the problem occurs once in two weeks and sometimes twice a week. What can cause this problem? Are there any DFS-R hotfixes available for server 2012 to resolve these problems?