I’m still have intermittent errors with my OneDrive backups. The “Stream was already consumed” error doesn’t happen on all of them, but the chances seem to be tied to the size of the backup. The more uploads it needs to do, the greater the likelihood that the error will occur… or at least that’s my non-scientific view of the thing.
Since OneDrive is basically unusable for my larger jobs on the current beta I decided to switch to the Rclone backend, which can then communicate with OneDrive. This had problems of its own though.
I had to use the old GUI to set up the job. For some reason, the Advanced options tab does not render correctly all the time for the Rclone backend. It’s supposed to look like this, with the Advanced options available at the bottom:
Instead though, it sometimes looks like this, with no Advanced options available at all:
I think that this has something to do with how the settings window is accessed. If you are on an existing backup and switch from another backend to Rclone, it will render the Advanced options. If your backup job is already set to the Rclone backend, the Advanced options renders blank.
Also, it seems to always set the Remote repository to all lowercase. Remotes in Rclone are case-sensitive, and in my case it’s “OneDrive”, not “onedrive”.
I was able to configure the jobs in the old GUI, but if I then opened it up and re-saved it under the new one I’m not sure all my settings would survive intact.
Once I got it all dialed in though, the Rclone backend seems to be working great … the job has been running for hours (10 Mbps upload :/), and has not encountered any errors yet.