Robocopy generates a detailed text report upon completion that displays the source and destination paths, total files copied, bytes transferred, and elapsed time. Understanding this output allows you to verify successful transfers, identify skipped files due to errors or exclusions, and troubleshoot issues by analyzing the summary statistics provided at the end of the command execution.
Understanding the Robocopy Output Structure
When you runrobocopy in Windows 10, the command-line interface outputs information in real-time as it processes each file and directory. However, the most critical data is presented in the final summary block. This section aggregates all actions taken during the session, providing a high-level overview of the operation's success or failure. The report typically begins with header lines showing the source and destination directories, followed by a list of individual file operations if verbose logging is enabled.
The core of the report consists of statistical counters. These include the number of files successfully copied, the total size of those files in bytes, and any extra files found at the destination that were not present in the source. Additionally, the report lists files that were skipped, either because they already existed and matched the copy criteria, or because an error occurred during the transfer process. This structure helps administrators quickly assess whether the backup or migration task completed as intended without manually checking every single file.
Key Metrics in the Summary
The summary block uses specific keywords to denote different outcomes. "Copied" indicates a file was successfully written to the destination. "Skipped" means the file was ignored based on the options provided, such as using the/XO (exclude older) flag. "Extra" refers to files present in the destination but not in the source, which is useful when comparing directory structures. "Failed" highlights files that encountered errors, such as permission denied or access issues, requiring immediate attention.
Interpreting File Counts and Bytes Transferred
One of the primary reasons users analyze the Robocopy report is to verify the integrity of the data transfer. The "Bytes" line shows the total amount of data moved. If this number matches the expected size of the source folder, it is a strong indicator that the copy was successful. Discrepancies here might suggest that some files were truncated or failed to write completely. Similarly, the file count provides a quick sanity check. If you expect to copy 1,000 files and the report states "1,000 Files Copied," the operation likely succeeded. However, it is important to note that Robocopy may skip files that are identical to those already at the destination if you use mirror mode (/MIR) or copy-only modes without overwriting flags. Therefore, a lower file count than expected does not always mean an error; it could mean the files were already present and unchanged.
For more details on how to interpret these counts and measure performance, see our guide on [How to Measure Robocopy's Copy Speed and Files Skipped/Copied?](/news/1399766/robocopy-copy-speed-files-skipped-copied).
Analyzing Extra Files and Skipped Items
The concept of "Extra" files is particularly relevant when using the/MIR switch, which mirrors the source directory tree exactly. In this mode, any file in the destination that does not exist in the source is marked for deletion. The report will list these under "Extra Dir" or "Extra File." If you are not using mirror mode, extra files are simply noted for informational purposes.
Skipped files are another common point of confusion. They often appear when using switches like /XC (exclude changed), /XN (exclude newer), or /XO (exclude older). If you are syncing a backup drive where you only want to update modified files, Robocopy will skip unmodified files to save time. The report clearly distinguishes between these intentional skips and actual errors, allowing you to filter out noise from your analysis.
Troubleshooting Common Report Anomalies
Sometimes the report may indicate failures even when files appear to be present at the destination. This can happen due to attribute mismatches, such as read-only flags or hidden attributes, depending on the switches used. For instance, if you do not use the/R:0 switch to set retries to zero, Robocopy might wait for network timeouts before marking a file as failed, leading to longer processing times and potentially confusing logs.
Another common issue is related to long path names. Windows has historically had a 260-character limit for paths, although Windows 10 and later versions support long paths if enabled in the registry or Group Policy. If your report shows many failures related to path length, ensure that long path support is active on both the source and destination systems.
If you are moving files rather than just copying them, understanding the implications of deletion is crucial. Learn more about safe deletion practices in [Safe Delete: Instantly Move and Delete Files in Windows](/news/1232377/instant-file-deletion-in-windows).
Logging and Saving the Report
By default, Robocopy outputs its report to the console window. To preserve this information for future reference or auditing, you should redirect the output to a log file using the/LOG: or /NFL and /NDL switches combined with standard output redirection. Using robocopy ... /log:C:\path\to\log.txt creates a clean, readable file containing the full summary. This is essential for large-scale migrations where manual verification of thousands of files is impossible.
Additionally, appending to existing logs with /LOG+: allows you to track multiple runs of the same job over time. This can be helpful for diagnosing intermittent network issues or tracking progress across scheduled tasks. Always review the exit codes returned by Robocopy alongside the log file, as these numeric codes provide a concise summary of the overall status, ranging from success (0) to various types of errors.
For insights into handling subdirectories and complex folder structures, refer to [How to Use Robocopy to Search Subdirectories Inside Source Folder Files and Move Them?](/news/1094057/robocopy-search-subdirectories).
Frequently Asked Questions
What does the 'Exit Code' in Robocopy mean?
The exit code is a numerical value returned after the command finishes, indicating the overall status. A code of 0 means no files were copied, 1 means files were copied successfully, 2 indicates extra files were found, and higher numbers represent various errors like access denied or retry limits exceeded.
Why are some files listed as 'Skipped' instead of 'Copied'?
Files are skipped when they match exclusion criteria defined by switches like /XO (exclude older) or /XC (exclude changed). This typically happens during incremental backups where only new or modified files need to be transferred to save time and bandwidth.
How can I view a summary without seeing every individual file?
You can suppress the display of individual file names by adding the /NFL (no file list) and /NDL (no directory list) switches to your command. This reduces clutter and focuses the output on the final summary statistics and any errors.
What should I do if the report shows 'Access Denied' errors?
Access denied errors usually stem from insufficient permissions on either the source or destination folders. Ensure you are running the command prompt as an administrator and that your user account has read/write access to both the source directory and the target location.
Can Robocopy report show me the speed of the transfer?
While Robocopy does not display a live speed meter in the standard report, you can calculate the average speed by dividing the total bytes copied by the elapsed time shown in the summary. For more precise speed metrics, consider using third-party tools or enabling verbose logging to analyze timestamps of individual files.