Skip to content

Commit 6b124f9

Browse files
Simplify RoboCopy usage explanation
Removed unnecessary explanation about RoboCopy behavior and its output interpretation.
1 parent e88bbb3 commit 6b124f9

1 file changed

Lines changed: 0 additions & 6 deletions

File tree

articles/storage/files/storage-files-migration-nas-hybrid-databox.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -121,12 +121,6 @@ Data Box documentation specifies a Robocopy command. That command isn't suitable
121121

122122
[!INCLUDE [storage-files-migration-robocopy](../../../includes/storage-files-migration-robocopy.md)]
123123

124-
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. To correctly interpret the results, review the file status in the command output:
125-
- Newer: File data is copied to the destination.
126-
- Modified: Only metadata is updated; file data isn't recopied.
127-
128-
In both cases, RoboCopy might report byte counts as though data was transferred. This behavior can lead to confusion when validating copy operations.
129-
130124
## Phase 6: Deploy the Azure File Sync cloud resource
131125

132126
Before you continue with this guide, wait until all of your files have arrived in the correct Azure file shares. The process of shipping and ingesting Data Box data will take time.

0 commit comments

Comments
 (0)