locked
Azcopy fails when copy vhds between storage on different azure subscriptions RRS feed

  • Question

  • Hi,

    I am trying to move a 127GB vhd between blob storage on two different accounts. I have been trying to use azcopy as from the research I have conducted this is apparently a good and simple method of achieving this. The format of the command I am issuing in the Windows Azure Storage tool is:

    azcopy https://<storage 1 name>.blob.core.windows.net/vhds
    https://<storage 2 name>.blob.core.windows.net/vhds 
    /sourcekey:<storage 1 key> 
    /destkey:<srorage 2 key> /S

    From what I have read this seems to be the correct format and is accepted in the tool. But after a few seconds, the tool fails with "Copy status: failed". However, on the destination machine, the vhd is present but has zero bytes. So it seems to be seeing the storage but failing in the transmission. Does anyone have any ideas why this is failing please? 



    Monday, March 24, 2014 2:46 PM

Answers

  • Hi Ivan,

    Your suggestion has helped me to find out what the problem was. As it turns out it was something really stupid on my part as apparently the VM has to be stopped for azcopy to work. I hadn't realised this as I had managed to download the VHD without doing this (didn't want to risk deallocating the external IP).

    So thanks to you and Will for your assistance and my apologies if I wasted your time. Good to have it working.

    Regards

    Steve.


    Thursday, March 27, 2014 4:06 PM

All replies

  • Hi Steve,

    Yes, base on my experience, your script is right format. Did you try to use other tools to login and download or move files ?  From the dashboard (http://www.windowsazure.com/en-us/support/service-dashboard/) shown, a small subset of storage requests in the East US region may experience higher latencies. I guess it may be due to this problem.

    For test purpose, I suggest you could try to use Azure Storage Explore (http://azurestorageexplorer.codeplex.com/) to view and download files. Any latest info, please let me know free.

    Regards,

    Will


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, March 25, 2014 9:55 AM
  • Hi Will,

    Thank you for your reply. My VM's are currently in the north Europe region so I don't think they are affected but I will take that potential issue into account in future. Thanks.

    I did try the Azure Management Studio with which I managed to download the VHD, albeit over several hours. But the main advantage of azcopy seems to be that I should be able to transfer directly between storage at a much faster rate.

    I will also try your suggestion regarding the Azure storage explorer. I'm currently evaluating the Cloudberry explorer for blob storage which failed to copy with error: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature." I don't know yet if this is an issue with the software or my accounts. Especially as the transfer started OK under azcopy.

    Thanks

    Steve.

    Tuesday, March 25, 2014 10:21 AM
  • hi Steve,

    I tested azcopy on my side. And I try to use http and https to transfer data. It works fine. And I didn't use the SAS token on the blob storage.

    I suggest you could try to use http. And at the same time, you need make sure your Primary Access Key is right.

    And if your or another blob storage have used SAS token, I recommend you see this blog (   http://blogs.msdn.com/b/windowsazurestorage/archive/2013/09/07/azcopy-transfer-data-with-re-startable-mode-and-sas-token.aspx ) for more details.

    Hope it helps.

    Will 


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Wednesday, March 26, 2014 6:02 AM
  • Look, that might be a similar problem. The CopyBlob shared access signature can expire during async copy. If you try to copy a big file (which VHDs usually are), the presigned URL for source file must be viable for a sufficient amount of time, not only for the moment of the initiating request.

    PS: As for problem with CloudBerry, please contact the support using Tools->Diagnostic dialog.

    Sincerely,

    IP

    Thursday, March 27, 2014 11:22 AM
  • Hi Ivan

    Thanks for taking the time to reply.

    I don't think this is a timeout issue, it fails within a couple of seconds of starting.

    Regards

    Steve.

    Thursday, March 27, 2014 2:25 PM
  • Check the x-ms-copy-status-description header contained in the response to a status check request (You can use http links and a network sniffer if azcopy doesn't do the required logging)
    • Edited by IvanP_CBL Thursday, March 27, 2014 3:37 PM
    Thursday, March 27, 2014 3:34 PM
  • Hi Ivan,

    Your suggestion has helped me to find out what the problem was. As it turns out it was something really stupid on my part as apparently the VM has to be stopped for azcopy to work. I hadn't realised this as I had managed to download the VHD without doing this (didn't want to risk deallocating the external IP).

    So thanks to you and Will for your assistance and my apologies if I wasted your time. Good to have it working.

    Regards

    Steve.


    Thursday, March 27, 2014 4:06 PM