While exploring the Office 365 Import Service in my test lab I encountered repeated timeout errors trying to upload PST files to Azure using AzCopy.exe.
[2015/07/26 23:26:36.206+10:00] >>>>>>>>>>>>>>>> [2015/07/26 23:26:36.221+10:00][VERBOSE] 3.1.0 : AzCopy /source:\\mgmt\pst /dest:https://uploadurl.blob.core.windows.net/ingestiondata/ /DestKey:****** /S /V:C:\Admin\PSTupload.log [2015/07/26 23:26:39.680+10:00][VERBOSE] Start transfer: Alan Reid.pst [2015/07/26 23:26:40.352+10:00][VERBOSE] Start transfer: Dawn Evans.pst [2015/07/26 23:26:40.352+10:00][VERBOSE] Start transfer: Elaine West.pst [2015/07/26 23:26:40.352+10:00][VERBOSE] Start transfer: Vik Kirby.pst [2015/07/26 23:41:41.552+10:00][VERBOSE] Transfer FAILED: Alan Reid.pst. [2015/07/26 23:41:41.568+10:00][ERROR] Alan Reid.pst: The client could not finish the operation within specified timeout. The client could not finish the operation within specified timeout. [2015/07/26 23:52:41.450+10:00][VERBOSE] Transfer FAILED: Elaine West.pst. [2015/07/26 23:52:41.450+10:00][ERROR] Elaine West.pst: The client could not finish the operation within specified timeout. [2015/07/26 23:52:41.450+10:00][VERBOSE] Transfer FAILED: Vik Kirby.pst. [2015/07/26 23:52:41.450+10:00][ERROR] Vik Kirby.pst: The client could not finish the operation within specified timeout. [2015/07/26 23:53:23.429+10:00][VERBOSE] Transfer FAILED: Dawn Evans.pst. [2015/07/26 23:53:23.429+10:00][ERROR] Dawn Evans.pst: The client could not finish the operation within specified timeout. The client could not finish the operation within specified timeout. [2015/07/26 23:53:23.445+10:00] Transfer summary: ----------------- Total files transferred: 4 Transfer successfully: 0 Transfer skipped: 0 Transfer failed: 4 Elapsed time: 00.00:26:47
I was trying to upload using my home internet connection, which doesn’t have high upload speed. The upload process was also showing a transfer speed of 0 KB/s. Clearly it was not making any progress.
Reviewing the AzCopy command line options I saw that there is a /NC parameter that can be used to control the number of concurrent operations.
AzCopy by default starts a certain number of concurrent operations to increase the data transfer throughput. Note that large number of concurrent operations in a low-bandwidth environment may overwhelm the network connection and prevent the operations from fully completing. Throttle concurrent operations based on actual available network bandwidth.
Lowering the thread count to 2 (by specifying /NC:2) seems to have resolved the issue for me, and the upload was able to finish on the next attempt.
This article PST Upload using AzCopy.exe Could Not Finish the Operation Within Specified Timeout is © 2015 ExchangeServerPro.com
Get more Exchange Server tips at ExchangeServerPro.com
