Rclone doesn’t have deduplication. That’s just finding files with the same name. It’s different from deduplication used in backup software.

Think of grinding data in a big machine, and removing blocks that are redundant. You may have every file to be a single copy, and get significant space reduction.

Rclone also has a hash-based dedupe mode. Still different from borg, but it can be a little more robust than name-based.

They also work together. restic uses rclone for backends other than the officially supported 7. rclone also has built-in restic integration.

rclone on it own is a syncing solution not backup.

>restic uses rclone for backends

This is cool. It sounds like I can set up restic to copy my backups to multiple S3 buckets, or even to an S3 bucket at the same time as a local drive using a union (https://rclone.org/union/) remote

rclone and restic are not direct alternatives. They have a slight overlap, but are also different. Rclone is more versatile for moving/copying files. Restic has snapshotting, pruning, client side encryption, deduplication, and compression. Restic actually supports rclone as a backend.

Restic also offers encryption and compression. That’s the selling point for me when dealing with dozens of TB