Bulk Internal Moves with Robocopy and Rsync

Moving a file server, relocating a department share, emptying a dying disk array: bulk internal moves are a different sport from daily transfer automation. The volumes are huge, the deadline is a cutover night, and users keep editing files while you copy them. The definition of success is absolute — nothing left behind, nothing silently different. Two free tools, robocopy on Windows and rsync everywhere else, have carried most of these migrations for decades.

This series treats the bulk move as the project it is. It covers how migrations differ from daily jobs, robocopy driven properly, and rsync applied to seed-and-delta moves. It covers the freeze-and-cutover night itself, and verification that proves completeness instead of assuming it. It covers the pitfalls - long paths, permissions, open files - that every migration meets. For rsync's day-to-day mechanics, our dedicated rsync series goes deeper; here we use it as a migration engine.

Articles in This Series

• Bulk Moves Are Not Daily Transfers: Planning the Big Copy
  This article explains why migrations play by different rules: volume, live users, one-shot cutovers. It covers the phase plan: inventory, seed copy, shrinking deltas, freeze, cutover, verify.
• Robocopy for Server Migrations, Properly
  This article explains the flags that matter in plain words, and the mirror switch and its dangers. It covers retries and multithreading, copying security and timestamps, logging, and a worked command evolution.
• Rsync for Bulk Moves and Seed-and-Delta Migrations
  This article covers rsync as a migration engine: the initial seed, repeated deltas that shrink toward zero, and the delete flag handled with respect. It covers preserving attributes, and local versus over-SSH moves.
• Seed, Delta, Freeze: Cutting Over Without Losing Files
  The cutover-night runbook: the final delta under a write freeze, repointing users and shares, rollback readiness, and the communication that keeps the night boring.
• Verifying Nothing Was Left Behind
  This article covers proof over hope: file and byte counts, hash sampling versus full verification, and dry-run modes as difference reports. It covers chasing the residue - open files, permission failures, path-length skips.
• Bulk Move Pitfalls: Long Paths, ACLs, and Open Files
  This article covers the classic wreckers: path-length limits, permissions that translate wrong, timestamp drift, hard links, and files in use. It also covers saturating the network during business hours - with a mitigation for each wrecker.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.