Automate Local Backups with Robocopy & Task Scheduler

Automate Local Backups with Robocopy & Task Scheduler​

Prerequisites​

• A Windows 10 or Windows 11 PC (any edition with Task Scheduler and Robocopy).
• A separate local destination drive or folder with sufficient space (e.g., an external USB drive or an internal second partition).
• Administrative rights to create and run scheduled tasks.
• Decide which folders to back up (e.g., Documents, Photos, Desktop). Robocopy works best when you script each source-destination pair or create a single batch that handles multiple pairs.

Step-by-step Instructions​

• Choose source folders you want to protect (common options: C:\Users\<You>\Documents, Desktop, Pictures, and important project folders).
• Choose a destination path on a separate drive (e.g., D:\Backups\Documents, D:\Backups\Pictures).
• Decide on backup policy: mirror (exact copy, including deletions) vs. incremental (add-new-or-modified-only). Robocopy’s /MIR mirrors the source to the destination, deleting files at the destination that no longer exist in the source; use with caution.

• Example:
  • D:\Backups\Documents
  • D:\Backups\Pictures
  • D:\Backups\Logs (for Robocopy logs)
• This keeps backups organized and makes it easier to manage space.

[USER=35331]@echo[/USER] off
set "src=C:\Users\YourName\Documents"
set "dst=D:\Backups\Documents"
set "log=D:\Backups\Logs\Documents-backup.log"

echo [%date% %time%] Starting Documents backup >> "%log%"
robocopy "%src%" "%dst%" /MIR /MT:16 /R:3 /W:5 /LOG+:"%log%" /TEE
echo [%date% %time%] Documents backup completed with exit code %errorlevel% >> "%log%"

• Customize the paths to match your setup.
• Explanation of key switches:
  • /MIR: Mirror source to destination (caution: deletes extraneous files in the destination).
  • /MT:16: Use multithreading (speed up to utilize multiple CPU cores).
  • /R:3 /W:5: Retry 3 times with 5-second waits on failed copies.
  • /LOG+: Appends to the log file; /TEE prints to console and log.
  • Quote paths to handle spaces.

[USER=35331]@echo[/USER] off
rem Documents
robocopy "C:\Users\YourName\Documents" "D:\Backups\Documents" /MIR /MT:16 /R:3 /W:5 /LOG+:"D:\Backups\Logs\Documents-backup.log" /TEE
rem Pictures
robocopy "C:\Users\YourName\Pictures" "D:\Backups\Pictures" /MIR /MT:16 /R:3 /W:5 /LOG+:"D:\Backups\Logs\Pictures-backup.log" /TEE

• Add the /L switch to a Robocopy command to simulate actions without copying:
  robocopy "%src%" "%dst%" /MIR /L
• Run the batch file from an elevated Command Prompt (Run as administrator) to verify the commands behave as expected before automating.

• Open Task Scheduler (search “Task Scheduler” in the Start menu).
• Create Basic Task (or Create Task for more options).
  • Name: Robocopy - Documents Backup (adjust as needed).
  • Description: Unattended backup of Documents to the external drive.
  • Trigger: Daily (or weekly) at a chosen time (e.g., 02:00 AM).
  • Action: Start a program.
  • Program/script: browse to the script, e.g., C:\Scripts\backup-documents.bat
  • Add arguments: (leave blank)
  • Finish: On the final screen, check “Open the Properties dialog for additional settings.”
• In the Task Properties:
  • General tab: Check “Run with highest privileges.”
  • Configure for: Windows 10/11 (your OS version).
  • If you’re backing up to a location that requires credentials, set the task to run whether the user is logged on or not, and provide a user account with access rights.
• Save and test:
  • In Task Scheduler, right-click the task and choose “Run” to test.
  • Check the log file in D:\Backups\Logs to confirm success and review any errors.

• After the first run, inspect the destination folders to confirm files exist and timestamps look sane.
• Keep a simple retention rule: e.g., keep last 30 backups or keep daily backups for a fixed window. With Robocopy /MIR, you’ll typically manage retention by the destination drive’s capacity and periodic manual cleanup unless you implement a rotation scheme in your scripts.

• If you want to spread load or back up additional folders, duplicate the task with updated script paths and schedules (e.g., Documents at 2:00 AM, Pictures at 3:00 AM).

Tips & Troubleshooting​

• Test with a dry run first: Always run Robocopy with the /L switch to simulate without writing. This helps catch path mistakes and wrong switches.
• Be careful with /MIR: It deletes files in the destination that no longer exist at the source. If you want a non-destructive backup, omit /MIR and use /E to ensure all subfolders are copied without deleting extra files on the destination.
• Use quotes for paths with spaces: Robocopy is robust, but you must quote paths that include spaces (e.g., "C:\Users\Your Name\Documents").
• Use /XD to exclude folders you don’t want backed up (e.g., cache folders or OneDrive app folders):
  robocopy "%src%" "%dst%" /MIR /XD "C:\Users\YourName\AppData" "C:\Users\YourName\Downloads\Temp"
• Check permissions: If the scheduled task runs while you’re not logged in, ensure the task uses an account with access to both the source and destination. Run with highest privileges.
• Logs are your friend: Keep a separate log per backup target or a consolidated log. Review logs periodically for unexpected errors (permissions, disk space, long paths, or special characters in file names).
• Handle long paths: If you encounter path length issues, enable the Windows long path support or shorten folder names for the backup scope.
• Space management: Make sure the destination drive has ample free space before enabling /MIR. Robocopy may create a large amount of data during initial runs.
• If the backup fails due to a locked file, Robocopy will retry (default: 1 million retries, with exponential backoff). Limit retries with /R:n and /W:n to avoid long delays.

Conclusion​

• Regular, unattended backups that run even when you’re away.
• Customizable scope and retention to fit your needs.
• Clear logs to monitor success and diagnose issues quickly.

• Robocopy + Task Scheduler provides a robust, cost-free backup solution on Windows 10/11.
• Start with a test run and dry-run (using /L) to avoid accidental data loss.
• Use separate scripts/tasks for different backup targets to keep things simple and predictable.
• Keep logs and monitor disk space to ensure long-term reliability.