Hi,

i have a Replication Group Setup with a lot of sharing violations (accessed files) and lately i also saw a list of backlogged files. I also noticed, that a small txt file i created wasnt replicated either. It took a few hours and everything was replicated, so in General it works.

My question: is it safe to say, that when having a large amount of sharing violations and backlog files that also normal files will be queued at the end of the Journal/list and not treated with Preference ? Also in normal circumstances those not accessed files would be replicated very fast, but due to backlogs delayed ?

thanks for clarification.

Marcus

Hi Marcus,

With enough sharing violations though, DFSR can start spending more time retrying locked files than it does replicating unlocked ones, to the detriment of performance.

To determine the real state of the file, use the DFSRDIAG BACKLOG command to check for sharing violations. The command output provides a list of the first 100 files that are not replicated.

You could refer to the article below to troubleshoot the issue.

Top 10 Common Causes of Slow Replication with DFSR
http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx

Best Regards,

Mandy