I have a single hub and spoke DFS replication topology that is replicating VHDs to a number of branch office servers. Replication is in sync on all servers except for one. Looking at the DFS Replicated Folders performance counter shows a very large number of file installs retried (~6,000) within the last 24 hours. There is currently a backlog of 11 files to the spoke.
Any ideas on how to get this remaining member server to sync up?
I've applied all DFS-R related hotfixes and registry entries per http://support.microsoft.com/kb/968429. Both points are running Windows Server 2008 R2. Staging space on both ends is equal to the total size of all VHDs in the replicated folder. File sizes range from 20GB to 60GB.
DFSR logs persistently indicate the following:
20140909 06:59:36.712 5988 SRTR 957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{BED1A741-D855-4EDD-96EA-17283CFB57CE} csId:{30BD2E2E-272D-4FF5-A737-8160E1E9946C} Error:
+ [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 5988 C The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 5988 C The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 5988 C The content set is not ready]