Skip to content

Commit 43d1231

Browse files
authored
Update storage-files-migration-robocopy.md
1 parent f1caef1 commit 43d1231

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ RoboCopy, as a trusted, Windows-based copy tool, has the home-turf advantage whe
3333

3434
AzCopy, on the other hand, has only recently expanded to support file copy with some fidelity and added the first features needed to be considered as a migration tool. However, there are still gaps and there can easily be misunderstandings of functionality when comparing AzCopy flags to RoboCopy flags.
3535

36-
An example: *RoboCopy /MIR* will mirror source to target - that means added, changed, and deleted files are considered. An important difference to *AzCopy -sync* is that deleted files on the source will not be removed on the target. That makes for an incomplete differential-copy feature set. AzCopy will continue to evolve. At this time AzCopy is not a recommended tool for migration scenarios with Azure file shares as the target.
36+
An example: *RoboCopy /MIR* will mirror source to target - that means added, changed, and deleted files are considered. An important difference of *AzCopy -sync* is that deleted files on the source will not be removed on the target. That makes for an incomplete differential-copy feature set. AzCopy will continue to evolve. At this time AzCopy is not a recommended tool for migration scenarios with Azure file shares as the target.
3737

3838
## Migration goals
3939

0 commit comments

Comments
 (0)