AzCopy Could Not Finish the Operation Within Specified Timeout

AzCopy Could Not Finish the Operation Within Specified Timeout

Recently I’ve started to use Azure cheap Blob storage as a backup repository for some of my important files and family photographs.  I’ve been using AzCopy to get my files from my PC to Azure and have come across the issue where AzCopy says “Could Not Finish the Operation Within Specified Timeout”.

At first I thought this was because of home internet connection not being the best, however after reading the AzCopy documentation I realised a switch within the command line could help solve my issue.

By default when AzCopy starts it creates a certain amount of concurrent connections in order to increase the data transfer throughput, unfortunately this large number of connections can overwhelm a low bandwidth network and cause the whole operation to fail.  In order to avoid this specifying the NC switch within our command can avoid this.

Your command to copy files to Azure should look like this:

AzCopy /Source:E:\Photos /Dest:https://azureurl.blob.core.windows.net/photos/ /DestKey:securekey /S /V:E:\upload.log /NC:1

The Source is where your files are.
The Dest is where your files are going in Azure.
The DestKey is the access key that is generated by Azure.
The S switch ensures AzCopy takes all files and subfolders.
The V switch is used to specify a log file destination.
The NC switch specifies how many concurrent sessions to use, in this case I’ve throttled it to one.

Use Azure Blog Storage, is a great way of creating an “off site” backup of your important documents, family photos etc.

 

Please follow and like us:
0
Comments are closed.