A Complete Guide to Robocopy
Robocopy is a powerful command-line tool for Windows that allows users to synchronize files and folders from one location to another. Learn more about everything you can do with Robocopy here.
Table of Contents
- What is Robocopy?
- How Robocopy works
- Robocopy examples
- Copying files and folders with Robocopy
- Moving files and folders with Robocopy /move
- How to filter files and folders
- Synchronizing files and folders with Robocopy /mir
- How to monitor backups with Robocopy /mon and /mot
- How to transfer files across a network
- How to use Robocopy Jobs with /save
- Robocopy vs PowerShell
- Additional features of Robocopy
What is Robocopy?
Robocopy stands for “Robust File Copy.” It is a powerful (and potentially scary) command-line utility to copy or move files from one place to another. It is a favorite amongst many IT Pros, mostly due to its overwhelming number of useful features and switches.
It was built to be more robust (hence the name) than Xcopy or the original copy command. Robocopy was first released with the Windows NT 4.0 Resource Kit (!). It has been a standard ‘feature’ in Windows since Windows Vista and Windows Server 2008.
What’s the difference with XCopy?
The biggest difference between Robocopy and Xcopy is the bewildering number of features, switches, flags, etc. There have also been several performance enhancements to Robocopy, making it a more pseudo-like backup utility compared to Xcopy.
How Robocopy works
As I’ve already stated several times, Robocopy contains a robust set of options, switches, and flags to be as meticulous as you need for all your file transfer tasks that land on your plate. Let’s go through all these lovely options together!
Robocopy is like a Swiss Army Knife for system administrators who need perform any kind of file operations on Windows. You can use it to:
- Copy files from one folder to another on the same device
- Copy files across a network and resume the operation if there’s a network failure (hence the name Robust File Copy)
- Perform and monitor backups
- Keep two folders synchronized
- Copy file attributes, NTFS permissions, auditing info, and more
- Skip NTFS junction points
- Perform copy operations with multithreading for increased performance
- Copy files if the administrator doesn’t have access rights
Note: These tables are directly from Microsoft’s docs.microsoft.com article as part of the tool’s main documentation site.
Why don’t we just let you utilize this lovely table to get a handle on the complete, but always growing, number of options around the basics of copying? Enjoy. (POP quiz in about 10 minutes!) 🙂
|/s||Copies subdirectories. This option automatically excludes empty directories.|
|/e||Copies subdirectories. This option automatically includes empty directories.|
|/lev:||Copies only the top n levels of the source directory tree.|
|/z||Copies files in restartable mode. In restartable mode, should a file copy be interrupted, Robocopy can pick up where it left off rather than re-copying the entire file.|
|/b||Copies files in backup mode. Backup mode allows Robocopy to override file and folder permission settings (ACLs). This allows you to copy files you might otherwise not have access to, assuming it’s being run under an account with sufficient privileges.|
|/zb||Copies files in restartable mode. If file access is denied, switches to backup mode.|
|/j||Copies using unbuffered I/O (recommended for large files).|
|/efsraw||Copies all encrypted files in EFS RAW mode.|
|/copy:||Specifies which file properties to copy. The valid values for this option are:D – DataA – AttributesT – Time stampsS – NTFS access control list (ACL)O – Owner informationU – Auditing informationThe default value for this option is DAT (data, attributes, and time stamps).|
|/dcopy:||Specifies what to copy in directories. The valid values for this option are:D – DataA – AttributesT – Time stampsThe default value for this option is DA (data and attributes).|
|/sec||Copies files with security (equivalent to /copy:DATS).|
|/copyall||Copies all file information (equivalent to /copy:DATSOU).|
|/nocopy||Copies no file information (useful with /purge).|
|/secfix||Fixes file security on all files, even skipped ones.|
|/timfix||Fixes file times on all files, even skipped ones.|
|/purge||Deletes destination files and directories that no longer exist in the source. Using this option with the /e option and a destination directory, allows the destination directory security settings to not be overwritten.|
|/mir||Mirrors a directory tree (equivalent to /e plus /purge). Using this option with the /e option and a destination directory, overwrites the destination directory security settings.|
|/mov||Moves files, and deletes them from the source after they are copied.|
|/move||Moves files and directories, and deletes them from the source after they are copied.|
|/a+:[RASHCNET]||Adds the specified attributes to copied files. The valid values for this option are:R – Read onlyA – ArchiveS – SystemH – HiddenC – CompressedN – Not content indexedE – EncryptedT – Temporary|
|/a-:[RASHCNET]||Removes the specified attributes from copied files. The valid values for this option are:R – Read onlyA – ArchiveS – SystemH – HiddenC – CompressedN – Not content indexedE – EncryptedT – Temporary|
|/create||Creates a directory tree and zero-length files only.|
|/fat||Creates destination files by using 8.3 character-length FAT file names only.|
|/256||Turns off support for paths longer than 256 characters.|
|/mon:||Monitors the source, and runs again when more than n changes are detected.|
|/mot:||Monitors the source, and runs again in m minutes, if changes are detected.|
|/MT||Creates multi-threaded copies with n threads. n must be an integer between 1 and 128. The default value for n is 8. For better performance, redirect your output using /logoption.The /mt parameter can’t be used with the /ipg and /efsraw parameters.|
|/rh:hhmm-hhmm||Specifies run times when new copies may be started.|
|/pf||Checks run times on a per-file (not per-pass) basis.|
|/ipg:n||Specifies the inter-packet gap to free bandwidth on slow lines.|
|/sl||Don’t follow symbolic links and instead create a copy of the link.|
|/nodcopy||Copies no directory info (the default /dcopy:DA is done).|
|/nooffload||Copies files without using the Windows Copy Offload mechanism.|
|/compress||Requests network compression during file transfer, if applicable.|
File Selection options
Alright, now we’ll present another nice table of all the ‘File Selection’ options in Robocopy.
|/a||Copies only files for which the Archive attribute is set.|
|/m||Copies only files for which the Archive attribute is set, and resets the Archive attribute.|
|/ia:||Includes only files for which any of the specified attributes are set. The valid values for this option are:R – Read onlyA – ArchiveS – SystemH – HiddenC – CompressedN – Not content indexedE – EncryptedT – TemporaryO – Offline|
|/xa:||Excludes files for which any of the specified attributes are set. The valid values for this option are:R – Read onlyA – ArchiveS – SystemH – HiddenC – CompressedN – Not content indexedE – EncryptedT – TemporaryO – Offline|
|/xf ||Excludes files that match the specified names or paths. Wildcard characters (* and ?) are supported.|
|/xd ||Excludes directories that match the specified names and paths.|
|/xc||Excludes changed files.|
|/xn||Excludes newer files.|
|/xo||Excludes older files.|
|/xx||Excludes extra files and directories.|
|/xl||Excludes “lonely” files and directories.|
|/im||Include modified files (differing change times).|
|/is||Includes the same files.|
|/it||Includes tweaked files.|
|/xc||Excludes existing files with the same timestamp, but different file sizes.|
|/xn||Excludes existing files newer than the copy in the source directory.|
|/xo||Excludes existing files older than the copy in the source directory.|
|/xx||Excludes extra files and directories present in the destination but not the source. Excluding extra files will not delete files from the destination.|
|/xl||Excludes “lonely” files and directories present in the source but not the destination. Excluding lonely files prevents any new files from being added to the destination.|
|/is||Includes the same files. Same files are identical in name, size, times, and all attributes.|
|/it||Includes “tweaked” files. Tweaked files have the same name, size, and times, but different attributes.|
|/max:||Specifies the maximum file size (to exclude files bigger than n bytes).|
|/min:||Specifies the minimum file size (to exclude files smaller than n bytes).|
|/maxage:||Specifies the maximum file age (to exclude files older than n days or date).|
|/minage:||Specifies the minimum file age (exclude files newer than n days or date).|
|/maxlad:||Specifies the maximum last access date (excludes files unused since n).|
|/minlad:||Specifies the minimum last access date (excludes files used since n) If n is less than 1900, n specifies the number of days. Otherwise, n specifies a date in the format YYYYMMDD.|
|/xj||Excludes junction points, which are normally included by default.|
|/fft||Assumes FAT file times (two-second precision).|
|/dst||Compensates for one-hour DST time differences.|
|/xjd||Excludes junction points for directories.|
|/xjf||Excludes junction points for files.|
Here is a good set of options to help keep your Robocopy command more robust and reliable.
|/r:||Specifies the number of retries on failed copies. The default value of n is 1,000,000 (one million retries).|
|/w:||Specifies the wait time between retries, in seconds. The default value of n is 30 (wait time 30 seconds).|
|/reg||Saves the values specified in the /r and /w options as default settings in the registry.|
|/tbd||Specifies that the system will wait for share names to be defined (retry error 67).|
For the next set, let’s go over the list of Logging options available in Robocopy.
|/l||Specifies that files are to be listed only (and not copied, deleted, or time stamped).|
|/x||Reports all extra files, not just those that are selected.|
|/v||Produces verbose output, and shows all skipped files.|
|/ts||Includes source file time stamps in the output.|
|/fp||Includes the full path names of the files in the output.|
|/bytes||Prints sizes, as bytes.|
|/ns||Specifies that file sizes are not to be logged.|
|/nc||Specifies that file classes are not to be logged.|
|/nfl||Specifies that file names are not to be logged.|
|/ndl||Specifies that directory names are not to be logged.|
|/np||Specifies that the progress of the copying operation (the number of files or directories copied so far) will not be displayed.|
|/eta||Shows the estimated time of arrival (ETA) of the copied files.|
|/log:||Writes the status output to the log file (overwrites the existing log file).|
|/log+:||Writes the status output to the log file (appends the output to the existing log file).|
|/unicode||Displays the status output as Unicode text.|
|/unilog:||Writes the status output to the log file as Unicode text (overwrites the existing log file).|
|/unilog+:||Writes the status output to the log file as Unicode text (appends the output to the existing log file).|
|/tee||Writes the status output to the console window, as well as to the log file.|
|/njh||Specifies that there is no job header.|
|/njs||Specifies that there is no job summary.|
Let’s have a look at how to actually use Robocopy with some practical examples.
Copying files and folders with Robocopy
Alright, it looks like I bombarded you with all these options, switches, and flags, Oh my! Let’s get to some examples of copying files with Robocopy.
I am using a Windows 11 client machine in my Windows Server 2022 Active Directory domain lab environment.
The following command will (not really) back up the files in the first location to the file server (G: drive). I used the /quit switch to verify that what Robocopy intends to do is correct.
Robocopy c:\Backup_Files g:\folder01 /quit
This command shows the Source and Destination ‘root’ locations, what files to backup, and then the options it will use. Everything looks good, now let’s run it!
Robocopy c:\Backup_Files g:\folder01
Notice that only one file was copied, the single TXT file in the root of c:\Backup_Files. This is because subdirectories are not backed up by default. So, the next step is to include subdirectories.
How to include subfolders with Robocopy /e
We can include subfolders with the /e switch to include all subdirectories, even empty ones.
robocopy c:\Backup_Files g:\folder01 /e
Looking at the summary below, 18 total files were discovered in the source, and 17 were copied because we already copied that single file in the root of the source. As a result, one file was skipped.
Moving files and folders with Robocopy /move
Instead of copying the files, we can move them using the /move switch.
robocopy c:\Backup_Files g:\folder01 /move /e
I checked my C: drive and the files are indeed gone. They are now on the G: drive.
How to filter files and folders
I doubt you won’t always want to copy ALL the files from one place to another. You will want to filter what files get copied.
Next, I’ll go through the most prevalent switches to select files by name, type, size, etc., all by using wildcard characters.
Selecting files by name or file type
We can use wildcards to choose specific filenames. As you can see, the command below with the asterisk only copied the files starting with the letter ‘m’.
robocopy c:\Backup_Files g:\folder01 m* /e
We can also choose to copy only PDF files with the command below.
robocopy c:\Backup_Files g:\folder01 *.pdf /e
Selecting files by file size using Robocopy /max
To address the need to choose files by size, let’s use this command with the /max switch to only copy files under 1MB.
robocopy c:\Backup_Files g:\folder01 /e /max:1000000
Here, 26 files under 1MB were copied and 10 were skipped because they were larger.
Selecting files by modification date with Robocopy /maxage
If we only wish to copy files that are less than a year and a half old, we can use the /maxage switch.
robocopy c:\Backup_Files g:\folder_01 /e /maxage:547
There were 4 files skipped here because they were older than 1.5 years old (or 547 days).
Synchronizing files and folders with Robocopy /mir
We can use the powerful and potentially impactful /mir (MIRror) command to keep two locations in sync. Each time you run this command, anything not exactly the same in both the source and destination will be rectified.
In practice, if you delete a file from the source, it will also be deleted in the destination (gone from both!). Moreover, if someone deletes a file in the destination, it will be also deleted in the source (gone from both!). Yes, powerful and scary, so use this command with care.
robocopy c:\Backup_Files g:\folder_01 /e /mir
I ran the command, and it did nothing as both locations were the same. I deleted one file from the source and ran it again.
As you can see above, there was an ‘EXTRA File’ found. So, naturally, Robocopy deleted it also in the destination. Interesting choice of words, wouldn’t you say?
How to monitor backups with Robocopy /mon and /mot
If you have a dire need for a ‘should be good enough for our needs right now’ backup service in a pinch, Robocopy has a few tricks up its sleeve. You can use the /mon and /mot switches to monitor for changes. After a specified number of file changes and amount of time, Robocopy will make another pass and get your files backed up again.
robocopy c:\Backup_Files g:\folder_01 /e /mon:3 /mot:5
As you can see at the bottom of this capture, the ‘Monitor’ is running, waiting for both 5 minutes and 3 file changes to take place. Using my DeLorean, I made at least three changes and went five minutes in the future…
You’ll notice Robocopy ran again and copied a file, skipped most, and also found an extra file in the destination. Pretty slick!
How to transfer files across a network
|/zb||This switch will copy files in restartable mode, letting it pick up from an interrupted copy session if a network path is slow, or unreliable. The ‘B’ option helps you overcome locked down ‘read’ permissions on the source by letting you at least copy ALL files.|
|/copyall||To ensure your files are able to be opened and changed in your new fileserver, for example, use this so all file permissions are copied along with the files. You’ll want your users to be able to seamlessly access all their files after your new fileserver is in place!|
|/rh||This will restrict Robocopy from running during certain hours. If you have a huge fileserver migration project and you don’t want your network connection (especially a WAN) to be saturated during business hours, use this little wonder.|
|/mt||Use this to help boost the number of threads Robocopy will instruct the CPU to use, to help the performance of your copies.|
How to use Robocopy Jobs with /save
Here’s another Robocopy feature I was unaware of – Jobs. You can save a rather complex Robocopy command for later use using the /save switch at the end. Here is an example.
robocopy c:\Backup_Files g:\folder_01 m* /e /max:1000000 /maxage:400 /save:"c:\Temp\BackupJob1"
The image above is the output of the text file Robocopy creates. Now, to run this specific Job/string in the future, you utilize the /job switch as so.
Robocopy vs PowerShell
Although you inherently get a lot of power in using PowerShell to handle the same basic copy/move file tasks mentioned here, again, the number of options available to you with Robocopy makes it the perfect choice if you want to handle file copy tasks efficiently and safely. Robocopy is a wonderful option for new file server creation and migration projects as well.
There are advantages and disadvantages in using Robocopy for your file operation and migration projects – the same can be said for PowerShell. Robocopy is a lean, mean, command-line program that runs compiled binary code. This is the main reason it is so fast, especially when using /mt:16 or more to utilize more application threads in Windows.
But where Robocopy is fast, PowerShell is certainly more robust in terms of how many tasks you can get done in a single PowerShell line of cmdlets or in a script. Being able to grab current file status, pipe that to another cmdlet to perform another function on a subset of those files, and output the results to a log file…the possibilities, as with everything PowerShell, are endless.
A good number of PowerShell’s file operation cmdlets are poorly implemented, or use unoptimized code. If you use the same .NET methods that PowerShell is using, you can get much higher performance, which can be quite perplexing.
To demonstrate, albeit on a small scale, the performance difference between Robocopy and PowerShell, I recorded a short video showing two file copy operations running simultaneously. I copied about 2000 files consisting of around 600 MB. Granted – this is not very scientific, but I just wanted to show the differences between the two. When you see the time savings Robocopy offers, at this very small scale, you can see where seconds saved here can amount to hours saved on larger-scale projects and file server migrations!
Let’s see how things go.
Go ahead and watch a short video I made of the operation:
Additional features of Robocopy
There are a few more features and attributes of Robocopy. Let me go through them here with you one by one.
When Robocopy runs, there are exit codes written out to the console or the log output file that explain if there were any errors or warnings along the way. Here are the most common exit codes:
|Error / Exit Code||Meaning|
|0||No errors have occurred, and no copying was performed. Both the source and destination are in perfect sync.|
|1||One oe more files were copied successfully. This should be the most common exit code for your projects.|
|2||Some Extra files or folders were detected. No files were copied though. You’ll see the details in the log output.|
|4||Some Mismatched files or folders were found. You may need to examine the log file for details to aleviate.|
|8||Some files or folders could not be copied. Check these errors in the log output.|
|16||This is a serious error. Robocopy did not copy any files. Usually due to permissions or an error in the source and destination directories.|
Long file names
When you’re copying files, you’ll occasionally run into the file path of either your source or destination locations exceeding the NTFS 256-character limit. However, Robocopy will utilize UNC pathnames exceeding 256 characters.
But, it is best to attempt to shorten your destination file paths to avoid potential issues in the future accessing those paths and files using Windows Explorer.
Here is a quick table explaining what those lovely file attributes mean. I wasn’t aware of all of these myself.
|Letter Attribute||What they Mean|
|N||Not content indexed|
Junctions and Symbolic Links
When you use Robocopy /S, it will follow the source and copy the contents to a standard folder. This works with Directory Symbolic Links, Junctions, and Hard Links. This is typical of most backup software algorithms.
To exclude Junction points from being copied, you can use /XJ, /XJD, or /XJF. This prevents the source files from being copied. The Junction Point will not be copied, with or without the use of these flags.
Deduplicated files (Windows Server 2016 and higher)
Be careful when using the /MIR to mirror a system drive on Windows Server 2016, 2019, 2022, etc. Robocopy will try to delete the deduplication files from the \System Volume Information hidden folder if you also run in backup mode using /B or /ZB. It will have permission to delete those files. Either exclude the \System Volume Information folder with /XD or just don’t use /MIR!!!! 😉
By default, Robocopy will use 8 threads during the file compare, and copy steps. You can use /MT:16 to start your testing in finding the most optimal number of threads to give you the greatest efficiency and performance during larger projects.
Inter-Packet Gap /IPG switch
If you are running on a particularly slow network, or high latency network, you can limit network bandwidth by using the Inter-Packet Gap switch – /IPG:n. This will tell Robocopy to send packets of 64 KB with a delay of n milliseconds.
The following table explains the file classes that can be used to include/exclude files during your file copy operations.
|File Class||In source folder||In destination folder||Source/destination File last modified times||Source/Destination File Sizes||Source/destination File attributes|
|Newer||Yes||Yes||Source > Destination||n/a||n/a|
|Older||Yes||Yes||Source < Destination||n/a||n/a|
There are a few notes to make about NTFS permissions. Using /B, backup mode will allow Robocopy to override file and folder permission Access Control Lists (ACLs).
When you see ERROR 5, it will often be accompanied by a standard ‘Access is denied.’ This means the account you’re logged in with doesn’t have the necessary permissions in either the source or destination locations to read or write (or update). It is best to use /B to circumvent this issue. You essentially won’t need to worry about source permissions.
Robocopy will copy security information (ACLs) for files and folders, but will not copy security changes unless the file has also changed. Simply use the /SEC switch to refresh any and all ACL changes regardless if the file(s) were changed.
Low Free Space Mode (LFSM)
Microsoft engineers added the Low Free Space Mode /LFSM:n switch to assist IT Pros with larger file copy projects, especially pushing them to Azure File Sync cloud storage locations. The switch works best for tiered storage destinations which might run out of free space before the Robocopy command finishes.
Robocopy will pause whenever a file copy would cause the destination volume’s free space to go below a percent value of its total size. You use the n variable for this amount. The default is 10%.
Remember – the /LFSM switch is NOT compatible with /MT, /B, /ZB, and /EFSRAW options.
When using the /MOVE or /PURGE switches to delete empty folders by setting the source and destination to the same folder, this does not always work with nested empty folders. It will only work if Windows Explorer is closed. You may need to reboot your server or workstation to make sure things are ‘clean’ in Explorer land.
Be careful when copying files larger than 2 GB from some iSCSI or SAN volumes. The operation may stall out filling up all available RAM. When the RAID controller’s settings are set to write-through caching vs write-back caching. Using other file copy utilities may be faster in this scenario as they will copy in larger blocks. But, lots of small files will slow them down where Robocopy normally shines. Use the /IPG switch (above) to alleviate this issue.
If you use the /FAT option to copy files into a directory with long filenames, and any short filenames happen to match in source and destination, those files will be replaced, which is logical. However, those files will retain their long filenames from the source even if they don’t match the long filenames of the source file. This needs to be examined carefully.
Robocopy is a wonderful file copy utility every IT Pro should keep in their arsenal. It is continually being enhanced with new features, even on Windows 11, and we hope this guide gives you some ideas about how to integrate Robocopy into your workflow.
More in Windows Server
Microsoft Releases Fix for Hyper-V VM Issues in Windows Server
Dec 21, 2022 | Rabia Noureen
Microsoft to Fix New Bug Breaking Hyper-V VMs in Windows Server
Dec 16, 2022 | Rabia Noureen
Microsoft Rolls Out Fix for LSASS Memory Leak Bug Affecting Windows Server
Dec 14, 2022 | Rabia Noureen
Action1 Review – Free Cloud-Native Patch Management for Windows
Dec 5, 2022 | Michael Reinders
Latest Patch Tuesday Updates Cause Freezes, Reboots on Domain Controllers
Nov 25, 2022 | Rabia Noureen
Microsoft Releases Fix for Kerberos Authentication Issues on Domain Controllers
Nov 18, 2022 | Rabia Noureen
Most popular on petri