Multiple Online Storage Sync

What is the problem you are having with rclone?

I am running Zorin OS (Linux) and using rclone to synchronize my local data to multiple cloud storage providers. However, I am running into synchronization issues when trying to handle these multiple remotes at the same time. I need to know the proper way to sync to multiple destinations without causing data conflicts, hitting API rate limits, or skipping files. Specifically, should I run separate sequential sync commands, run them concurrently, or look into a union/combine backend type?

Run the command 'rclone version' and share the full output of the command.

rclone v1.69.0
- os/version: ubuntu 22.04 (64 bit) (Zorin OS 17)
- os/kernel: 6.5.0-27-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.1
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Multiple storages (Google Drive, OneDrive, and Dropbox)

The command you were trying to run (eg rclone copy /tmp remote:tmp)

# I am looking for the proper way/command to sync to multiple remotes safely on Linux, for example:
rclone sync /home/user/data gdrive:backup && rclone sync /home/user/data onedrive:backup

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[gdrive]
type = drive
scope = drive
token = XXX

[onedrive]
type = onedrive
token = XXX
drive_id = XXX
drive_type = personal

[dropbox]
type = dropbox
token = XXX

welcome to the forum,

should run rclone selfupdate to get lastest version of rclone.


that is up to you.
i prefer to keep it simple, so i do not use union/combine.


one main reason you are hitting api limits - none of your remotes are using not client id+secret
as explained at Making your own client_id

Hi,

The best place for you to start is creating a client ID for Google and Microsoft as well.

As it was announced to all we are all going to have to use our own client ID for Google at some point this year anyway so there's no reason to not start right now.

That may very well solve your problem.

You're gonna have to do it eventually anyway.