rclone

Overview

rclone is an open-source command-line sync tool started in 2014 by Nick Craig-Wood in the United Kingdom and maintained continuously since. It speaks 70+ storage backends including S3, B2, Wasabi, Google Drive, OneDrive, SFTP, and WebDAV, which makes it the universal adapter of the Backup & Migration space.

Its value is composability. Scheduling comes from cron or a systemd timer, encryption from rclone crypt or restic, verification from rclone check, and one set of commands builds a local-to-offsite-object-storage pipeline with no commercial console and no per-seat fee.

The cost is that you must understand your own data flow. sync deletes extra files at the destination while copy does not, and mixing them up is a leading cause of data incidents, while misconfiguration produces silent failures, so check runs and log alerts are not optional.

Core Strengths

• 70+ backends mean a cross-cloud migration is two remote configs rather than a rewrite
• Subcommands including sync, copy, check, and mount cover sync, verification, and mounting
• The crypt backend layers client-side encryption over any storage so keys never reach the provider
• A single binary with no runtime dependencies runs on small VPS instances or containers at zero licence cost

Product Ecosystem

Subcommand semantics

copy adds and updates only, sync deletes extra destination files, and check compares hashes for consistency. Backups must use copy, or sync with a backup directory, to keep mirroring separate from incremental retention so a wiped source does not wipe the destination.

Encryption and multi-cloud migration

The crypt backend encrypts names and content alike for client-side encryption over any object store. Cross-cloud moves typically copy to a new remote, run check, then switch traffic rather than syncing directly, preserving a rollback path.

Drawbacks

• A command-line tool with a steep learning curve where a misused sync deletes destination files
• No built-in scheduling or monitoring, so cron, logs, and alerting are yours to build
• Large-file and high-concurrency runs need manual tuning of transfers and checkers to avoid provider throttling
• No GUI or audit log, which forces an extra change-management process for teams

Use Cases

• Backing sites up to object storage (★★★★★) - With cron plus B2 or Wasabi it becomes a zero-licence offsite pipeline
• Cross-cloud data migration (★★★★★) - Two remotes plus copy and check is the most controllable migration route
• Client-side encryption needs (★★★★☆) - The crypt backend keeps keys off the provider, suiting sensitive data
• Teams needing GUI and audit (★★) - No UI or audit trail, so process must be built around it

Pricing

rclone itself is free, so all cost sits in storage and bandwidth. The real investment is operations time for tuning, alerting, and restore drills, which usually outweighs any software licence in the evaluation.

FAQ

• What is the difference between sync and copy? copy only writes and updates, while sync deletes extra destination files to make both sides identical. For backups use copy or sync with a backup directory, otherwise a source-side deletion propagates and the backup stops being a backup.

• How do I know backups are intact? Run rclone check periodically to compare hashes and sample real restores. Exit codes alone are insufficient, since network interruptions and permission errors can leave files missing while reporting success.

• Why is large-file sync slow? Tune transfers and checkers, enable fast-list to cut request counts, and use a backend with multipart upload. Slow runs are usually throttling from excessive concurrency rather than insufficient bandwidth.