Skip to content
anavem.com logoanavem.com logo
About
LatestAll updates
Windows ServerTutorials

How to Configure DFS-R Folder Replication on Windows Server 2025

Set up DFS-R folder replication between Windows Server 2025 systems with unidirectional and multidirectional configurations, staging optimization, and verification.

By Emanuel De Almeida

5 min read
Difficulty
Intermediate
Time required
30-60 minutes
Steps
8
Platform
Windows Server
Version
2025
DFS-R folder replication across multiple Windows Server 2025 systems, with synchronized folders, replication paths.
View full image
Table of contents

Quick Answer

Go to the steps

Install FS-DFS-Replication, create a group, add members, configure staging, start sync.

  1. Install DFS-R on all servers.
  2. Create shared folders with matching permissions.
  3. Create replication group and add members.
  4. Set primary member and configure schedule.
  5. Verify with Get-DfsrBacklog.
Command
Install-WindowsFeature -Name FS-DFS-Replication, RSAT-DFS-Mgmt-Con -IncludeManagementTools

Expected result: Folders synchronized with RDC compression.

Key takeaways

  • How to install DFS-R, create replication groups, configure members and schedules, and verify health.
  • DFS-R keeps folders synchronized for redundancy and branch office access with efficient bandwidth usage.
  • Ensure identical NTFS permissions, use RDC for WAN links, and monitor backlog regularly.

Introduction

DFS Replication (DFS-R) synchronizes folders between servers using block-level Remote Differential Compression (RDC). Per Microsoft Learn, it is an active-active replication engine replacing FRS.

DFS-R supports hub-and-spoke and full mesh topologies on NTFS volumes with Active Directory. This tutorial covers the complete setup on Windows Server 2025.

Who this is for: Windows Server administrators setting up file replication between domain-joined servers.

Before you start

Access
Domain Admin or DFS administrator.
Required roles
  • Domain Admin
Required licenses
  • Windows Server 2025
Environment
Two or more domain-joined Windows Server 2025 systems with NTFS volumes.
Vendor
Microsoft
  • Administrator permissions required

30-60 minutes plus initial sync time.

Warning: DFS-R is not a backup solution

DFS-R replicates deletions and corruption. Implement a proper backup strategy alongside DFS-R.

Warning: Create a backup before initial sync

Initial sync designates one server as authoritative. Conflicting data on secondaries moves to ConflictAndDeleted.

1Install DFS Replication role

Install DFS-R on all servers.

Run Install-WindowsFeature on each server. Per Microsoft Learn, DFS-R works on Desktop Experience and Server Core. Verify with Get-WindowsFeature.

PowerShell
Install-WindowsFeature -Name FS-DFS-Replication, RSAT-DFS-Mgmt-Con -IncludeManagementTools

Expected result: Install State: Installed.

Note

Use Invoke-Command for remote installation on multiple servers.

2Create and share replicated folders

Set up identical folders and shares.

Create directories and SMB shares on all servers. Set matching NTFS permissions with Set-Acl.

PowerShell
New-SmbShare -Name ReplicatedData -Path D:\ReplicatedData -FullAccess 'Domain Admins'

Expected result: Share accessible with matching permissions.

Note

Mismatched permissions cause failures. Verify on all servers.

3Create the replication group

Define the replication group.

Use DFS Management (dfsmgmt.msc) or PowerShell. Choose data collection for unidirectional, multipurpose for full mesh.

PowerShell
New-DfsReplicationGroup -GroupName DataReplication -DomainName yourdomain.com

Expected result: Group created.

Note

Use descriptive names including direction and purpose.

4Add members and configure primary

Add servers and set primary.

Add members. Set primary with Set-DfsrMembership -PrimaryMember $true on the source server.

PowerShell
Add-DfsrMember -GroupName DataReplication -ComputerName SERVER01,SERVER02

Expected result: Members added. Primary set.

Note

Only one primary in unidirectional. No primary in multidirectional.

5Configure schedule and bandwidth

Control replication timing.

Use full bandwidth for LAN (default). For WAN, throttle to 70% during business hours. Changes propagate through AD DS in up to 60 minutes.

Expected result: Schedule configured.

Note

Allow full bandwidth overnight for catch-up.

6Configure staging quota and RDC

Optimize performance.

Set staging quota and enable RDC. RDC replicates only changed blocks. Set conflict quota with -ConflictAndDeletedQuotaInMB.

PowerShell
Set-DfsrMembership -GroupName DataReplication -FolderName ReplicatedData -ComputerName SERVER01 -StagingPathQuotaInMB 10240

Expected result: Staging and RDC configured.

Note

For 100+ MB files, set staging to 20-30% of largest file size.

7Start initial synchronization

Start the first sync.

Restart DFSR service on all members. Create a test file. Monitor with Get-DfsrBacklog. Check event log for Event ID 4104.

PowerShell
Get-DfsrBacklog -SourceComputerName SERVER01 -DestinationComputerName SERVER02 -FolderName ReplicatedData

Expected result: Test file appears. Event 4104. Backlog 0.

Note

Initial sync can take hours for large datasets.

8Verify replication

Confirm replication works.

Create test file on primary. Verify on secondaries. Check Get-DfsrState and Get-DfsrBacklog. Monitor for events 4104/4614.

PowerShell
Get-DfsrState -ComputerName SERVER01,SERVER02

Expected result: State: Normal. Backlog: 0.

Note

Growing backlog indicates performance or connectivity issues.

How to Confirm Replication Works

Verify fix

Create a test file on primary. It should appear on secondaries within minutes. Run Get-DfsrBacklog to verify 0 pending files. Check event log for Event IDs 4104 and 4614.

Normal result: Backlog 0. Events 4104/4614 logged.

Abnormal result: Check DFSR service, firewall rules, and AD DS health.

Healthy

Backlog: 0

All synchronized.

Growing backlog

Backlog increasing

Check bandwidth or staging.

Stalled

Service stopped

Restart DFSR.

Troubleshooting

Backlog keeps growing

Warning

Cause: Bandwidth, firewall, or staging quota issues.

Check firewall rules. Increase staging quota. Verify network connectivity.

Related step 7: Start initial synchronization

Initial sync never completes

Critical

Cause: Large dataset or DFSR stopped.

Check DFSR service. Verify AD DS health. Pre-seed with robocopy for very large datasets.

Related step 7: Start initial synchronization

File conflicts

Warning

Cause: Simultaneous edits on different servers.

Check ConflictAndDeleted folder. Implement file locking. Consider unidirectional.

Related step 7: Start initial synchronization

Permission denied errors

Warning

Cause: Mismatched NTFS permissions.

Verify identical NTFS permissions on all servers. DFSR runs as Local System by default.

Related step 2: Create and share replicated folders

Frequently asked questions

What firewall ports does DFS-R need?

TCP 135 (RPC), TCP/UDP 445 (SMB), and dynamic RPC 49152-65535.

Unidirectional vs multidirectional?

Unidirectional has one primary distributing to read-only replicas. Multidirectional lets all servers modify files with higher conflict risk.

Does DFS-R support ReFS?

No. Per Microsoft Learn, DFS-R only supports NTFS.

Is DFS-R a backup solution?

No. DFS-R provides redundancy, not backup. It replicates deletions too.

How to fix staging quota exceeded?

Increase quota with Set-DfsrMembership -StagingPathQuotaInMB. Set to 20-30% of largest file size.

Conclusion

Install the role, create a replication group, add members, configure schedule and staging, then verify with Get-DfsrBacklog.

Ensure identical NTFS permissions, use RDC for WAN links, and monitor backlog regularly.

Main path
Install > New-DfsReplicationGroup > Add-DfsrMember > Set-DfsrMembership > Get-DfsrBacklog

Sources3

Reader actions
Was this helpful?
Rate this articleRate
7 readers viewed this article

Reader reviews

Rate this articleBe the first to rate
No written reviews yetRate the article above, or be the first to share your experience.

More to explore