Backrest vs Duplicacy
Pros and cons
Each app's own strengths and weaknesses, plus the specs where Backrest and Duplicacy differ.
Backrest
Pros
- Standard restic repositories
- Encrypted, deduplicated snapshots
- Single small Go binary
- Pre and post backup hooks
- Completely free
Cons
- Prune needs significant memory
- Per-repository deduplication only
- Prune locks repository exclusively
Duplicacy
Pros
- Lock-free concurrent backups
- Cross-computer deduplication
- Wide storage backend support
- Snapshot-style revisions
Cons
- Web UI needs paid licence
- Proprietary storage format
- CLI has no scheduler
Which suits you
| Spec | ||
|---|---|---|
| Price | Advantage: Free | Free + Commercial |
| Licence | Advantage: GPL-3.0 | Custom (free for personal use) |
| Architecture | x86 + ARM | x86 + ARM |
| Runtime | Go | Go |
| Database | SQLite | none |
| Containers | 1 (app only) | 1 (app only) |
| Install options | Docker + Linux, macOS, Windows | Docker + Linux, macOS, Windows |
| Clients | – | macOSWindowsLinux |
| Concurrent backups | Sequential / locked | Lock-free |
| Storage support | Local, SFTP, S3, B2, rclone | Local, SFTP, S3, B2, WebDAV |
| Notifications | Discord, Slack, Gotify, Shoutrrr, Healthchecks | Email, Webhooks |
| Deduplication | Yes (per repository) | Global |