AzureStorageExplorer
AzureStorageExplorer copied to clipboard
I dont like this tool
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Problem
It is a pain to uploading big logs (+1GB) for partners.
- If I leave them overnight uploading, many times they fail for no reason.
- If upload during the day, they suck all my bandwidth and I barely able to work.
- Even though they suck all my bandwidth, they seem to never been able to complete upload.
Desired Solution
Sharefile site used to work a lot better
Alternatives and Workarounds
None, it is a pain on the ....
Additional Context
:(
@mcline1984 for your pain points:
- If you're seeing consistent transfer failures, feel free to attach logs for recent ones to this issue. We can take a look and try to see what is going on. You can find logs at
<your user directory>/.azcopy
. - There are settings available to help you reduce the amount of bandwidth used for transfers. You can go to Settings (gear on the left side) -> Transfers -> AzCopy to find those. I suggest looking at:
- Maximum transfer rate
- Network Concurrency (changing this to "Adjust dynamically" usually is of big help to people on slow networks)
- If you'd rather do your transfers on the command line, you can use AzCopy directly: https://github.com/Azure/azure-storage-azcopy
Please give the above consideration, and if you have any further feedback please don't hesitate to share. Thanks!
Hi
Thanks for your response. The only reliably solution I found is to use winrar to split large (1GB+) logs into 100mb pieces and upload them 1 by 1. This completes upload in a reasonable amount of time. Once in a while one 100mb piece may get stuck for which I will cancel and retry; however, this way I dont have to retry the entire log, but just one piece.
I will submit logs once I have time to try again large logs.
@mcline1984 files in the ranges of GB should be of no problem. So if you do find the time to try without splitting up, and then share any failure logs with us that'd be great. And of course, make sure you try tweaking the settings we suggested. :)