Hi - I have an all 2008R2 DFSR topology where 1 server is authoritative & all others are read-only members. I initially setup the 1-way replication incorrectly, and fixed it by following instructions linked from here:
Because that page also mentions "Did not maintain the DFSR service at the current patch level" as a common mistake, I had all applicable DFSR patches applied before I fixed the DFSR topology.
Now, some of my read-only member servers are reporting Backlogged Sending Transactions. My understanding is that this is bogus info (read-only members don't send any files) and can mostly be ignored. It can also be fixed by following instructions from here:
http://support.microsoft.com/kb/2645713
We are hesitant to disable the 8.3 filename creation though, and would prefer to leave it turned on. But this means that my read-only members potentially will never fully complete the initial synchronization. Does anyone know if this will be a problem? If so, is there some other way to fix read-only members so that their Backlogged Sending Transactions get cleared? Thanks!
(Also, it would be nice if the hotfix page for KB 2285835 would mention this 8.3 filename issue as something that the hotfix creates.)