Automatic Local Backups with Robocopy and rsync: How to Copy and Verify Them

In Windows, Robocopy can copy folders to a chosen location and run on a schedule. Automation executes defined instructions, but it is advisable to review the results of each operation.

A folder copy with Robocopy is not equivalent to a full system backup: it serves for selected files and folders, but not for restoring the entire computer. If you need to recover files prior to a change or deletion, check if the method retains versions.

In Windows, Robocopy allows copying files and directories from the command line and scheduling their execution. The chosen instructions and options determine what is copied; review the Microsoft documentation on Robocopy to adapt the command to your case.

The OuiHeberg guide describes using Robocopy to copy folders and schedule a task in Windows Server. When preparing your own configuration, check the source and destination paths and review the execution log. OuiHeberg: Copying folders with Robocopy

Define which folders you want to copy and what you need to be able to recover. Robocopy copies folders, but it does not replace a solution designed to restore the entire system. Ensure that the chosen method covers the type of recovery you need.

Robocopy allows copying selected folders, but a file copy does not by itself restore the entire system. Review the logs and test the restoration of files you need to recover. The OuiHeberg guide also presents the restoration test as part of its explanation of backups in Windows Server. OuiHeberg: Copying folders with Robocopy

Robocopy allows copying directories from the command line. The OuiHeberg guide offers an example to copy a folder and schedule its execution in Windows Server. Adapt the paths to the chosen computer and destination before running any command. Microsoft: Robocopy

/E includes subdirectories, even empty ones; /COPY:DAT requests copying data, attributes, and timestamps; /R:2 limits retries to two, and /W:5 sets a five-second wait between them. /LOG writes a log. Review the log after execution to know the result of the copy.

Avoid /MIR if you have not deliberately designed a mirror replica: it combines the inclusion of subdirectories with the deletion of items in the destination that are no longer in the source. For an initial setup, it is more prudent to copy without deleting and test the behavior with a test folder. Robocopy returns exit codes that combine different conditions; consult its documentation to interpret the obtained code. Microsoft: Robocopy exit codes

Open Task Scheduler, create a task with an appropriate schedule, and select the script or command as the action. Configure an account with sufficient permissions. If the destination is a USB drive, ensure it is connected at the scheduled time. Review the result of each execution to detect if the copy did not finish as expected. Microsoft: Task Scheduler

rsync allows copying files and directories between locations. Before running a copy, review the command options and confirm that the source and destination paths correspond to the intended locations. rsync: manual

To anticipate changes without applying them, add --dry-run and review the output. Once you have confirmed the source, destination, and options, remove that parameter to perform the transfer. --delete removes items in the destination that no longer exist in the source. Carefully check its effect before using it, especially if you want to preserve files deleted from the source. rsync: manual

If you schedule a task with cron, check its configuration and result on your system through a test run. crontab: Ubuntu documentation

Verification must answer two different questions: whether the task finished without errors and whether the copied files can be recovered. In Windows, review the Robocopy log and exit code; in Linux, keep the rsync output and check its completion status. A scheduled task without alarms is not sufficient proof if no one looks at its results.

To check selected files, you can calculate their cryptographic hashes in both the source and the copy and compare the results. A file comparison does not replace a restoration test: restore some files to another location and confirm that you can open them. rsync: manual

Perform a test restoration to a folder different from the source. Select several important files, confirm that they open, and compare their content; if the backup retains necessary permissions or metadata, check those attributes as well. Then document the procedure so that another person can repeat it. The valuable test is recovering data, not just seeing files on the destination disk. Repeat the exercise after significant changes to the script, system, or device.

If the storage contains sensitive data and can be lost or stolen, consider protecting the device or volume with encryption and store the recovery key separately, in a safe place.

A simple copy with Robocopy or rsync also does not necessarily provide historical versions, automatic retention, snapshot management, or full system recovery. You can reduce risk by keeping dated copies in separate destinations, using NAS snapshot functions if available, or adopting a backup tool that implements retention. Do not assume that a synchronization offers these features: review its behavior before trusting it with the only copies.

Before leaving the process running, use this brief list:

• Copy a test folder and confirm that the files appear in the destination.
• Simulate a deleted or modified file and check what happens to the copy.
• Disconnect the destination, run the task, and verify that the failure is logged.
• Restore one or more files to another location and open them.
• Periodically check available space, logs, and system changes.

Adjust the frequency of copies to the importance of the data and ensure you can restore them through a practical test.