Conclusion#

• A single Robocopy command can achieve ‘mirror backup + exclusion + Log + acceleration’, suitable for daily automated backups.

Where It’s Suitable For#

• Regular backups (daily / pre-CI backups)
• Large file synchronization (project folders)
• Scenarios requiring exclusion of temporary data like node_modules / bin
• Scenarios requiring preservation of permissions and timestamps

Process Steps#

1
robocopy "來源資料夾" "目的地資料夾" /mir

1
robocopy "來源資料夾" "目的地資料夾" /mir /xj /MT:100 /xf *.scc *.bak ^
2
  /xd "packages" "bin" "obj" "node_modules" ".vs" "TempFile" "Data" "history"

1
robocopy "來源資料夾" "目的地資料夾" /mir /xj /MT:100 /xf *.scc *.bak ^
2
  /xd "packages" "bin" "obj" "node_modules" ".vs" "TempFile" "Data" "history" ^
3
  /maxage:7 > .\Log\%dd%.log

Additional Notes#

• /mir will delete extra files in the destination. Misuse can directly ‘empty’ your destination.
• While /MT is fast, setting it too high might max out CPU or I/O. It’s recommended to start testing from 16-64.
• The %DATE% format is affected by system locale and may need adjustment across different machines.

Command / Example Summary#

1
:: 建立 Log 資料夾
2
if not exist ".\Log" mkdir ".\Log"
3

4
:: 產生日期（YYYYMMDD）
5
set dd=%DATE:~0,4%%DATE:~5,2%%DATE:~8,2%
6

7
:: 完整備份指令
8
robocopy "來源資料夾" "目的地資料夾" /mir /xj /MT:100 /xf *.scc *.bak ^
9
  /xd "packages" "bin" "obj" "node_modules" ".vs" "TempFile" "Data" "history" ^
10
  /maxage:7 > .\Log\%dd%.log

Wrapping Up#

• Robocopy isn’t difficult; the challenge lies in ‘parameter combinations’. This set of commands should cover 90% of backup scenarios.
• It’s recommended to run it in a test folder first to confirm the /mir behavior before deploying to a production environment.