Prepare a Robocopy pre-seed for DFS Replication

Source facts

Microsoft’s Robocopy procedure describes pre-seeding as a way to shorten DFS Replication’s initial synchronization when establishing replication, adding a partner, or replacing a server. It calls for a current Robocopy version appropriate to the operating system and for stabilizing the files so locked files do not block copying. Except when the source runs Windows Server 2003 R2, the procedure permits running Robocopy on either server.

Applicability

Identify the source of truth, destination, replication membership, and operating-system versions. Review the source’s version-specific instructions rather than treating its historical examples as a deployment inventory. A completed file-copy job should be evaluated separately from the later replication acceptance test.

DSE recommendation

Have a second administrator review the approved source and destination paths before starting the copy. Plan how writers will be paused or otherwise coordinated, and record which data remains subject to change. Retain the chosen options and a sanitized log. Investigate skipped files and access failures individually instead of accepting a successful-looking completion message alone.

Verification

Compare representative files, directories, and permissions between the approved endpoints. Reconcile all unexplained copy failures, then conduct a separate initial-synchronization review and controlled replication test. Ask the data owner to confirm the destination contents before the old server is retired or repurposed. Keep the copy log and replication evidence together, with their timestamps and reviewer names.

Official references

Microsoft Learn: Use Robocopy to pre-seed files for DFS Replication. Source reviewed September 8, 2026.