-
Notifications
You must be signed in to change notification settings - Fork 245
Description
Which version of the AzCopy was used?
AzcopyVersion 10.29.1
Which platform are you using? (ex: Windows, Mac, Linux)
OS-Environment linux
OS-Architecture amd64
What command did you run?
Command: sync https://xxx.file.core.windows.net/v-share001/?se=2025-07-04t01%3A00z&sharesnapshot=2025-07-03t01%3A00%3A13.0000000z https://yyy.file.core.windows.net/v-share002 --skip-version-check --preserve-smb-info=true --preserve-permissions --delete-destination=true --log-level=ERROR --exclude-path=tax
What problem was encountered?
The scanning phase of the Azcopy sync command takes huge time to complete. My expectation while using "--exclude-path" argument is that it skips the Scanning of the excluded path on both primary and DR storage.
Job 801be96e-b819-d74d-4dfa-d4eddf94b65f Summary
Files Scanned at Source: 8511620
Files Scanned at Destination: 1376721
Elapsed Time (Minutes): 191.2093
Number of Copy Transfers for Files: 5040
Number of Copy Transfers for Folder Properties: 5
Total Number of Copy Transfers: 5045
Number of Copy Transfers Completed: 5045
Number of Copy Transfers Failed: 0
Number of Deletions at Destination: 3863
Total Number of Bytes Transferred: 51420171690
Total Number of Bytes Enumerated: 51420171690
Final Job Status: Completed
How can we reproduce the problem in the simplest way?
The behaviour is default for all the azcopy sync command with --exclude-path arguments.
Have you found a mitigation/solution?
No