What is the problem you are having with rclone?
Maybe this is not a problem but instead a SOLUTION to a problem: I was plagued by extremely low upload speeds (around 100 KB/s) for several years when syncing borgbackup repositories to Backblaze B2. My problems were previously described in the (now locked) forum thread here. The underlying cause was found to be lots of 503 errors being throws by Backblaze while Backblaze support assured me that everything is OK at their end. None of the proposed solutions (e.g. increasing the --transfers value) worked.
Recently I have found that simply adding the "--fast-list" option to rclone command increased my upload speeds from around 100 KB/s to at least 2 MB/s (sometimes up to 5 MB/s). That's at least 20x speed increase ant it's absolutely consistent (tried 5 times without the --fast-list option and 5 times with it). I don't know if this is a bug in rclone or at Backblaze's end but this info might help other afflicted users.
N.B: My borgbackup repositories consist of multiple long files (up to 500MB) and many more short 17 bytes files (for snapshots that did not change compared to the previous snapshot). The typical file composition of my borgbackup repository can be seen here.
What is your rclone version (output from
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg
rclone copy /tmp remote:tmp)
rclone -vv sync /home/fuxoft/sklad_internal/backup/frantisek_borg/Lightworks b2:borgbackup-frantisek/Lightworks
The rclone config contents with secrets removed.
[b2] type = b2 #master account and key account = e06xxxxxxxx key = 00248xxxxxxxxxxxxxxxxxxxx #App key for borgbackup-frantisek app - works since rclone 1.43 #key = K0023xxxxxxxxxxxxxxx #account = 002e06xxxxxxxxxxxxxx endpoint =
EDIT: Fixed missing "sync" directive in the command.