Windows Server / File Services, Storage & Backup
Check replicated file backlog before declaring a DFSR copy current
A file-server replica can be online but missing recent changes. Inspect the specific replication group, folder and direction.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DfsrBacklog -GroupName 'BranchData' -FolderName 'Department' -SourceComputerName FS01 -DestinationComputerName FS02 -VerboseRead the result
The query reports backlog information for this defined relationship. A point-in-time count does not guarantee the copy remains synchronized under continuing writes.
Resolve and verify
Correlate progress with DFSR events, staging capacity and network health. Repair the demonstrated dependency and validate representative files and timestamps.
Before changing production
Do not treat DFSR as a transactional database replication system or force an authoritative restore just because a backlog exists.