Skip to content

Commit 27f0ebf

Browse files
Update RoboCopy documentation for output clarity
Clarified RoboCopy output interpretation regarding file copy operations and metadata changes. Added recommendations for using Windows Server versions.
1 parent 4c323b7 commit 27f0ebf

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

articles/storage/files/storage-files-migration-robocopy.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,14 @@ robocopy <SourcePath> <Dest.Path> /MT:20 /R:2 /W:1 /B /MIR /IT /COPY:DATSO /DCOP
6969
| `/Z` | **Use cautiously** </br>Copies files in restart mode. This switch is recommended only in an unstable network environment. It significantly reduces copy performance because of extra logging. |
7070
| `/ZB` | **Use cautiously** </br>Uses restart mode. If access is denied, this option uses backup mode. This option significantly reduces copy performance because of checkpointing. |
7171

72+
RoboCopy might report that files were copied even when no data transfer was necessary. This behavior occurs because robocopy evaluates both file data and metadata changes when producing its output.
73+
74+
To correctly interpret the results, review the file status in the command output:
75+
- Newer: File data is copied to the destination.
76+
- Modified: Only metadata is updated; file data isn't recopied.
77+
78+
In both cases, RoboCopy might report byte counts as though data was transferred. This behavior can lead to confusion when validating copy operations.
79+
7280
> [!IMPORTANT]
7381
> We recommend using a Windows Server 2022 or newer. When using a Windows Server 2019, ensure at the latest patch level or at least [OS update KB5005103](https://support.microsoft.com/topic/august-26-2021-kb5005103-os-build-18363-1766-preview-4e23362c-5e43-4d8f-95e5-9fdade60605f) is installed. It contains important fixes for certain Robocopy scenarios.
7482

0 commit comments

Comments
 (0)