As per this documentation, this message is displayed if AzCopy is receiving "Server Busy" responses from Azure. (I.e. HTTP status 503). Seeing a few Server Busy messages is fine. AzCopy will automatically retry the affected operations, with an exponential delay.
Suggested steps in this case:
- If the message is displayed only infrequently and intermittently, it's probably normal and can be ignored.
- Otherwise, check your throughput against the publicly documented throughput and IOPS limits for the particular type of Storage Service that you are using. ( If using AzCopy at the default logging level, the number of IOPS achieved is shown near the end of the log file). If you are approaching the throughput or IOPS limits, then seeing this message is expected.
- If you are not approaching the throughput or IOPS limits, and you are seeing this message persistently, then check the documentation on High Throughput Block Blobs and Premium Block Blobs. If, after checking that documentation, it appears that you should not be seeing this message, please reach out to the support.
Additional reading:
If this doesn't help, it would help to get the following details to troubleshoot your issue further:
- The exact command line used, including the source and destination URLs
- The output of azcopy jobs show <job-id> --with-status=Failed
- The output of azcopy jobs resume <job-id> --with-status=Failed
- The output of azcopy jobs clean <job-id>
Alternatively, you can also check the link you provided (https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-optimize), which is a guide on how to optimize azcopy performance. It has some tips on how to adjust the concurrency value, the number of parallel operations, and the block size to improve the speed and reliability of your data transfer.
You can also use the --log-level flag to get more detailed information about your azcopy operation.
Let me know in the comments and we can investigate further. Thanks.