| Robocopy | |
| Other Names: | Robust File Copy for Windows |
| Developer: | Microsoft |
| Operating System: | Windows NT 4 and later |
| Included With: | Windows Vista and later |
| Genre: | Command |
| License: | Freeware |
Robocopy is a command-line file transfer utility for Microsoft Windows. Robocopy is functionally more comprehensive than the COPY command and XCOPY, but replaces neither. Created by Kevin Allen[1] and first released as part of the Windows NT 4.0 Resource Kit, it has been a standard feature of Windows since Windows Vista and Windows Server 2008.
Robocopy provides features not found in the built-in Windows COPY and XCOPY commands, including the following:
/XJ switch).SeBackupPrivilege, normally not available to standard user accounts) to bypass NTFS ACLs that would otherwise impede transfer (requires the /B switch).[2] [3]Since Windows Server 2019 and Windows 10, Robocopy supports SMB compression for transferring files across a network. If the /compress is specified, the destination computer supports SMB compression, and the files being copied are compressible, the operation enjoys significant performance improvements. The SMB compression adds inline whitespace compression to file transfers. Compression is also available with the [[XCOPY]] command and Hyper-V live migration with SMB.[7] [8]
Here are some examples of usage, which is not case-sensitive. If more than one option is specified, they must be separated by spaces.
/E):If directory names have non-standard characters, such as spaces, they must be enclosed in double quotes, as is usual in the command line.
/E), copy all file information (/COPYALL, equivalent to /COPY:DATSOU, D=Data, A=Attributes, T=Timestamps, S=Security=NTFS ACLs, O=Owner info, U=Auditing info), do not retry locked files (/R:0) (the number of retries on failed copies default value is 1 million), preserve original directories' Timestamps (/DCOPY:T - requires version XP026 or later):/MIR), copy files in resume mode (/Z) in case network connection is lost:For the full reference, see the Microsoft TechNet Robocopy page.[9]
Robocopy syntax is markedly different from its predecessors (copy and xcopy), in that it accepts only folder names, without trailing backslash, as its source and destination arguments. File names and wildcard characters (such as * and ?) are not valid as source or destination arguments; files may be selected or excluded using the optional "file" filtering argument (which supports wildcards) along with various other options.[10]
For example, to copy two files from folder c:\bar to c:\baz, the following syntax is used:
And to copy all PDF files from c:\bar to c:\baz:
The files named are copied only from the folder selected for copying; fully qualified path names are not supported.
CAUTION: A long-standing issue with Robocopy means that if you back up from the root folder of a drive [e.g., {{code|robocopy d:\ b:\d-backup\ ....}}], the destination files will be given attributes including SH. This means that they will be invisible to normal access (including DIR in cmd.exe). To fix this, add to the robocopy command line - or do an ATTRIB command to remove them afterwards.
Robocopy outputs to the screen, or optionally to a log file, the names of all the directories it encounters, in alphabetical order. Each name is preceded by the number of files in the directory that fulfill the criteria for being copied. If the directory does not yet exist in the target, it is marked "New Dir"; if the directory is empty and the /E option is not used, or it contains no files meeting the criteria, a new directory will not be created.
If the /NFL (no file names in log) option is not used, the files being copied will be listed after the name of the directory they are in.
At the end of the output is a table giving numbers of directories, files, and bytes. For each of these, the table gives the total number found in the source, the number copied (including directories marked "New Dir" even if they are not copied), the number skipped (because they already exist in the target), and the number of mismatches, FAILED, and extras. "Failed" can mean that there was an I/O error that prevented a file being copied, or that access was denied. There is also a row of time taken (in which the time spent on failed files seems to be in the wrong column).
Robocopy's "inter-packet gap" (IPG) option allows some control over the network bandwidth used in a session. In theory, the following formula expresses the delay (in milliseconds) required to simulate a desired bandwidth (in kilobits per second), over a network link with an available bandwidth of kbps:
D={BA-BD\overBA x BD} x 512 x 1000
In practice however, some experimentation is usually required to find a suitable delay, due to factors such as the nature and volume of other traffic on the network. The methodology employed by the IPG option may not offer the same level of control provided by some other bandwidth throttling technologies, such as BITS (which is used by Windows Update and BranchCache).
FILE_SHARE_READ[11] flag during opening. Normally Volume Shadow Copy Service is used for such situations, but Robocopy does not use it. Consequently, Robocopy is not suitable for backing up live operating system volumes. However, a separate utility such as ShadowSpawn[12] (under MIT License) or DiskShadow[13] (included with Windows Server 2008), can be used beforehand to create a shadow copy of a given volume, which Robocopy can then back up./MT[:n] option to enable multithreaded copying, the /NP option to disable reporting of the progress percentage for files is ignored. By default the MT switch provides 8 threads. The n is the number of threads you specify if you do not want to use the default.[16]Although Robocopy itself is a command-line tool, Microsoft TechNet provided a GUI front-end called Robocopy GUI. It was developed by Derk Benisch, a systems engineer with the MSN Search group at Microsoft, and required .NET Framework 2.0.[17] It included a copy of Robocopy version XP026. It is no longer available from Microsoft, but may be downloaded from the Internet Archive's Wayback Machine.[18]
There are non-Microsoft GUIs for Robocopy:
Ken Tamaru of Microsoft developed a copying program with functionality similar to Robocopy, called RichCopy, this was discontinued in 2010. It is not based on Robocopy, and does not require .NET Framework.[25]
All versions of Robocopy store their version number and release date in their executable file header, viewable with File Explorer or PowerShell. Some of them (not all) report their version numbers in their textual output.
| Product version | File version | Year | Bundled with |
|---|---|---|---|
| 1.54 | 1996 | Windows NT 4.0 Resource Kit | |
| 1.70 | 1997 | Windows NT Resource Kit | |
| 1.71 | 4.0.1.71 | 1997 | Windows NT Resource Kit |
| 1.95 | 4.0.1.95 | 1999 | Windows 2000 Resource Kit |
| 1.96 | 4.0.1.96 | 1999 | Windows 2000 Resource Kit |
| XP010 | 5.1.1.1010 | 2003 | Windows 2003 Resource Kit |
| XP026 | 5.1.2600.26 | 2005 | Robocopy GUI v.3.1.2 |
| XP027 | 5.1.10.1027 | 2008 | Windows Vista, Server 2008, 7, 2008 R2 |
| 6.1 | 6.1.7601 | 2009 | KB2639043 |
| Windows 8 and later, Windows Server 2012 and later |