Skip to main content

Restic vs Rsync vs Rclone

While these tools often appear in the same backup scripts, they solve fundamentally different problems. Many administrators confuse them or try to use one for everything. This guide clarifies the distinct role of each tool in a modern backup stack.

The Simple Summary
  • Rsync: Mirroring files between servers (Changes overwrite destination).
  • Rclone: Moving data to Cloud Storage (S3, GDrive, B2).
  • Restic: Versioned, encrypted backups with history (Snapshots).

Feature Comparison Matrix​

| Feature | Rsync | Rclone | Restic | | : | : | : | : | | Primary Goal | Synchronization | Cloud Movement | Archival / Backup | | Data Model | File-based (1:1) | Object-based (1:1) | Snapshot-based (N:1) | | History Retention | No (Overwrites) | No (Overwrites) | Yes (Deduplicated) | | Encryption | SSH Transport only | Optional (Crypt remote) | Mandatory (AES-256) | | Deduplication | No | No | Yes (Content-Aware) | | Cloud Support | No (SSH only) | Native (50+ backends) | Native + Rclone bridge | | Mountable? | No | Yes (rclone mount) | Yes (restic mount) |

1. Rsync: The Mirror​

Best For: Deployment, Migration, "Hot" Standby.

Rsync is designed to make Destination look exactly like Source. If you delete a file on the source, Rsync deletes it on the destination (with --delete).

Why use Rsync?​

  • Speed: It's the fastest way to move data between two Linux servers.
  • Simplicity: The destination files are just files. You can cd into the backup folder and read them.
  • Delta Transfer: Only sends changed blocks of a file.

Why NOT to use Rsync for Backups?​

  • Ransomware Vulnerability: If your server gets encrypted, the next cron job will sync the encrypted files to your backup server, overwriting the good files.
  • No Versioning: You rely on complex scripting (hard links cp -al) to keep history.
  • Storage Inefficiency: Storing 30 days of full backups consumes 30x the space.

2. Rclone: The Cloud Mover​

Best For: Offsite replication, Cloud Migration, Drive Mounting.

Rclone is "Rsync for Cloud Storage." It speaks the APIs of S3, Google Drive, OneDrive, Dropbox, and Backblaze B2.

Why use Rclone?​

  • Cloud Native: Uploads to cheap object storage (S3/Wasabi) easily.
  • Mounting: Can mount a Google Drive as a local filesystem.
  • Encryption: Can create an encrypted "crypt" layer on top of any cloud provider.

Why NOT to use Rclone for Backups?​

  • API Costs: Syncing millions of small files to S3 can cost a fortune in API requests.
  • No Deduplication: Uploading the same 10GB file twice stores 20GB.
  • Slow Metadata: Listing 1 million files on S3 takes a long time compared to a local index.

3. Restic: The Time Machine​

Best For: Disaster Recovery, Ransomware Protection, Long-term Retention.

Restic creates Snaphots. Each backup is a point-in-time view of your data. It feels like a full backup every time, but thanks to deduplication, it only stores the unique chunks.

Why use Restic?​

  • Efficient History: Keep hourly backups for a year with minimal storage growth.
  • Security: Everything is encrypted client-side. The cloud provider sees only blobs, not files.
  • Integrity: restic check verifies that your data is safe from bit rot.
  • Retention: Built-in policies (--keep-daily 7) handle cleanup automatically.

Why NOT to use Restic?​

  • Not for Sync: You cannot use Restic to deploy code to a server. It requires a restore operation.
  • Opaque Storage: You cannot browse the S3 bucket to see your files. You must use the Restic binary to read the data.

The Perfect "Hybrid" Strategy​

For a robust 3-2-1 backup strategy, use all three:

flowchart TD
    Source[Server Data] -->|rsync| LocalDir[Local Mirror]
    LocalDir -->|restic| LocalRepo[Local Restic Repo]
    LocalRepo -->|rclone| CloudRepo[Offsite Cloud Storage]
  1. Rsync: Mirror data from app containers to a local /backup directory (staging).
  2. Restic: Snapshot that /backup directory into a local repository for fast restores and history.
  3. Rclone: Sync the Restic repository files to Backblaze/S3 for disaster recovery.

This gives you:

  • Fast Recovery: Restore from local Restic repo instantly.
  • Disaster Recovery: If the building burns down, pull from Cloud.
  • History: Roll back to any point in time.
  • Efficiency: Deduplication saves storage costs.