none
Timeouts when Uploading with Azcopy

Toate mesajele

  • Hi,

    As far as I know if you are copying a file, the largest you can copy is the maximum BLOCK BLOB size of 195GB. I suggest you export your database dumps to multiple files so no single file is over 195GB.

    If the timeout issue keeps occurring in your machine, your network connection quality with global Azure might be awful. Please consider checking your proxy settings, creating the storage account in a region near China such as East Asia, or specifying a smaller /NC value in AzCopy command line (the default value is CPU core number * 8).

    Time-Out issue  might occur when you are copying large files. You could resume the transfer by running the same .\azcopy.exe command or you could use a script like the one below:

    [int]$Failed = $Result[5].Split(":")[1].Trim() $Journal = "$env:LocalAppData\Microsoft\Azure\AzCopy" $i=1 while ($Failed -gt 0) {     $i++     [int]$Failed = $Result[5].Split(":")[1].Trim()     $Result = .\AzCopy.exe /Z:$Journal     $Result     $i }

    Ref: http://blogs.msdn.com/b/windowsazurestorage/archive/2013/09/07/azcopy-transfer-data-with-re-startable-mode-and-sas-token.aspx

    For further information about AzCopy, please refer to http://aka.ms/azcopy .

    Hope this helps.

    Girish Prajwal

    28 ianuarie 2016 12:06
    Moderator
  • Hi,

    I have written a very simple batch file to resume AzCopy when there are file transfer failed.

    You can save it as a bat file, and change the AzCopy Command as you like.

    Please let me know if it works for you.

    Thanks!

    :START
    AzCopy /source:[source] /dest:[dest] /pattern:[pattern] /DestKey[key] /y /s
    if %errorlevel% LSS 0 goto START

    5 februarie 2016 02:24
  • The batch script to automatically resume worked for me. Thanks!
    11 iunie 2018 03:56
  • @Trufus,

    Thanks for the confirmation. 

    12 iunie 2018 18:24
    Moderator