DFSR replication is lagging or shows conflicts in the log.
DFSR works fine for SYSVOL and inter-office file replication, but stalls on huge files, antivirus corrupting the staging folder, or a too-small staging quota.
Try this first
- 1Check backlog: dfsrdiag backlog /rgname:rg /rfname:rf /smem:source /rmem:destination. Counts >10000 indicate a problem.
- 2Check staging folder size: the default 32 GB is too small for modern file shares. Increase to e.g. 80 GB, more if you have large files.
- 3Antivirus exclusions: DFSR Database (\System Volume Information\DFSR\) and the staging folder. Otherwise you get random 'sharing violation' errors.
- 4For SYSVOL specifically: a stuck SYSVOL replication sometimes needs an 'authoritative restore'. Microsoft has a KB with exact steps, do not improvise.
- 5On conflicts: one file wins, the other lands in ConflictAndDeleted. Communicate to users that they shouldn't edit the same file at two offices at once.
When to bring us in
For SMB environments still using DFSR for user data: consider moving to SharePoint Online or Azure Files with sync. DFSR was never meant for real-time multi-master collaboration.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.