This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I tried following Copy data from Amazon S3 to Azure Storage by using AzCopy | Microsoft Learn
As said on S3 Compatible API (backblaze.com
Access Key ID and Secret Access Key
For the purposes of terminology, the Application Key and Application Key ID are the equivalent of the Secret Access Key and Access Key ID respectively. For more information about App Keys, please see our documentation here.
So I got AWS_ACCESS_KEY_ID=<keyID> and AWS_SECRET_ACCESS_KEY=<applicationKey> from BackBlaze B2 > Account > App Keys > Add a New Application Key and set as environmental variables:
set AWS_ACCESS_KEY_ID=#########
set AWS_SECRET_ACCESS_KEY=##########
Finally:
azcopy copy 'https://s3.us-west-002.backblazeb2.com' 'https://<myaccount>.blob.core.windows.net/<container>' --recursive=true
or
azcopy copy "https://s3.us-west-002.backblazeb2.com" "https://<myaccount>.blob.core.windows.net/<container>" --recursive=true
Both got same errors:
INFO: Scanning...
INFO: Authenticating to destination using Azure AD
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support
failed to perform copy command due to error: cannot start job due to error: cannot scan the path \\?\C:\WINDOWS\system32\https:\s3.us-west-002.backblazeb2.com, please verify that it is a valid.
What I'm doing wrong?
Why when using "azcopy copy 'https://s3.us-west-002.backblazeb2.com'https://<myaccount>.blob.core.windows.net/<container>' --recursive=true" or "azcopy copy "https://s3.us-west-002.backblazeb2.com" "https://<myaccount>.blob.core.windows.net/<container>" --recursive=true" it parses the path "\?\C:\WINDOWS\system32\https:\s3.us-west-002.backblazeb2.com"?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 74%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Another straightforward solution is by the help of a third-party tool which can integrates fine with backblaze and Azure blob to transfer from/to both , and I suggest Goodsync , Gs Richcopy 360 and Macrium
If you're using a Windows Command Shell (cmd.exe), enclose path arguments with double quotes ("") instead of single quotes (''). See the reference here: storage-use-azcopy-s3
----------
--please don't forget to upvote and Accept as answer if the reply is helpful--
This happen either with " in CMD or ' in PowerShell
Edit: Also the same thing happens on Linux, so it isn't a problem with " or '
I see that you are not passing the SAS key required to authenticate. You can use it similar way like the following command
azcopy copy "https://s3.us-west-002.backblazeb2.com/<mybucketname>/" "https://mystorageaccount.blob.core.windows.net/mycontainer?sp=racwdl&st=2022-02-28T05:19:39Z&se=2022-02-28T13:19:39Z&spr=https&sv=2020-08-04&sr=c&sig=eyQTDWm0n4yfjL0kS620ABC2FcTpk2FLUzoOGzwfju8%3D" --recursive
where ?sp=racwdl&st=2022-02-28T05:19:39Z&se=2022-02-28T13:19:39Z&spr=https&sv=2020-08-04&sr=c&sig=eyQTDWm0n4yfjL0kS620ABC2FcTpk2FLUzoOGzwfju8%3D is the SAS key
I'm using SAS, I just omitted in the post for obvious reason. The problem is not with destination, but with source. If I use the same command, but for local files, i.e. "C:\foo.bar.docx" the command works fines. The problem is when using URLs, because for some reason it parses as a local file, so if I put any URL as a source, i.e. "https://foobar.com" it will parses as "C:\WINDOWS\system32\https:\foobar.com".
The same happens on linux where it parses as "/home/<user>/https:\foobar.com"