AzCopy /Source:https://sourceaccount.blob.core.windows.net/mycontainer1
/Dest:https://destaccount.blob.core.windows.net/mycontainer2
/SourceKey:key1 /DestKey:key2 /S
After using this script to migrate data from one container to another its shows an error:
unknown command "/source:https://karmsa.blob.core.windows.net/newcnt" for "azcopy"
while rest of the commands(copy, sync) are working fine.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@amitpoonia8142 Please use the latest version of Azcopy which have a different syntax: https://github.com/Azure/azure-storage-azcopy
@Adam-Smith-MSFT I am using version 10.3.1. Can you please share the syntax.
Sure, below is an example:
azcopy cp "https://[srcaccount].blob.core.windows.net/[container]/[path/to/blob]?[SAS]" "https://[destaccount].blob.core.windows.net/[container]/[path/to/blob]?[SAS]"
You can view all examples by typing the following command in cmd, where your azcopy.exe is located: azcopy copy -h , it will provide you with several examples of what is supported. Let me know if this resolves your question to close the case.
Thanks,
Adam
I got it @Adam-Smith-MSFT , you can close the case.
Thanks,
Amit
Might I recommend that attention is given to this link: https://docs.microsoft.com/en-us/microsoft-365/compliance/importing-pst-files-to-office-365#BKMK_NetworkUpload. The instructions and the version of the AzCopy tool that are linked from these instructions do not align. E.g. instructions say you should use /Source and /Dest parameters when in actuality you need to use the cp command.
@amitpoonia8142 Please use the latest version of Azcopy which have a different syntax: https://github.com/Azure/azure-storage-azcopy
I have to ask... why? Why does it have a totally different syntax? Why have you broken half the world's azure deployment scripts? Why wouldn't you simply give this thing a totally different name? Let people continue to download the old AzCopy and let others adopt this totally different program you've created in it's place? e.g... like RoboCopy vs Xcopy vs copy....
What you've done is like making RoboCopy but calling it Xcopy instead. Result: headaches for a lot of people.
Changing the syntax is one thing... But then seeing all the current documentation in the Import/Export process in O365 refer to the old syntax, while linking to the new version that uses a totally different syntax... That's a paddling
Most helpful comment
I have to ask... why? Why does it have a totally different syntax? Why have you broken half the world's azure deployment scripts? Why wouldn't you simply give this thing a totally different name? Let people continue to download the old AzCopy and let others adopt this totally different program you've created in it's place? e.g... like RoboCopy vs Xcopy vs copy....
What you've done is like making RoboCopy but calling it Xcopy instead. Result: headaches for a lot of people.