S3 to Azure Files: failed to parse user input due to error: the inferred source/destination combination is currently not supported. Please post an issue on Github if support for this scenario is desired
nkol opened this issue · 9 comments
Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
I'm using MAC and azcopy 10 I want to copy data from S3 bucket to my Fileshare using SAS tocken
navigate to installation directory of azcopy then:
./azcopy cp cp "https://wdw-mongo-backup.s3.eu-central-1.amazonaws.com/test/test.txt" "https://prodmongobackup.file.core.windows.net/prod-mongo-backup/S3/?SASTOKEN"
and then I get this issue:
failed to parse user input due to error: the inferred source/destination combination is currently not supported. Please post an issue on Github if support for this scenario is desired
can I copy to fileshare or only on blob storage?
S3 to fileShare is not currently supported. THe only supported target with S3 is blob, at present. The only workaround, with AzCopy, is to copy to blob and then copy (again) to the file share. Sorry.
@jincod I moved to a different team some time ago, so I'm not involved in AzCopy any more. Perhaps @adreed-msft or @zezha-msft can comment.
Sorry @jincod, we haven't been able to prioritize this feature request.
The workaround is to copy from S3 -> Blob -> Files. Is that a reasonable mitigation for you? Are you looking to migrate data regularly?
Hello @zezha-msft
Thank for the replay.
We need to migrate it regularly. So would be great to avoid Blob as a temp storage.
Is it hard to implement S3 -> Azure Files?
Is there any update on this? Has it been prioritised yet or is it still not on the current roadmap?
@ecrowe-aridhia sorry we have not prioritized this feature yet since there is a mitigation.