Backrest vs Borg
Editor take
Choose Backrest for a browser that schedules and restores, and for alerts without a script. Choose Borg for compression you can choose and for a 1.x line that began in 2016.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
Backrest
Where Backrest is stronger
- Schedules and restores in a browserPlans carry a cron schedule, retention and a snapshot browser, so a restore is a few clicks; Borg leaves scheduling to cron and restores from the command line.1
- Alerts without a wrapper scriptPosts to Discord, Slack, Gotify, Shoutrrr or Healthchecks when a plan fails; Borg exits non-zero, so the alert comes from cron or a script you write.2
- S3, B2 and rclone targetsWrites straight to S3, Backblaze B2, Azure, Google Cloud, SFTP or any rclone remote; a Borg 1.4 repository lives on a disk or an SSH host.3
Borg
Where Borg is stronger
- Compression you can choosezstd, lz4, zlib or lzma, picked on each borg create; Restic and Backrest compress with zstd only.4
- Append-only over plain SSHAn SSH key can run borg serve --append-only, so a compromised client cannot delete old archives; Restic needs rest-server, or rclone in front of the repository, for the same lock.5
- A 1.x line since 2016Borg ships 1.4.5 as its stable release, with 2.0 still beta; Restic, under Backrest, is at 0.19.1.6
Backrest vs Borg: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
| Spec | ||
|---|---|---|
| Price | Free | Free |
| Licence | GPL-3.0 | BSD-3-Clause |
| Concurrent backups | Sequential / locked | Sequential / locked |
| Storage support | Local, SFTP, S3, B2, rclone | Local, SSH |
| Notifications | Discord, Slack, Gotify, Shoutrrr, Healthchecks | – |
| Deduplication | Yes (per repository) | Yes (per repository) |
| Web UI | Yes | – |
| Docker | Yes | Yes |
| Linux package | Yes | Yes |
| Windows | Yes | – |
| macOS | Yes | Yes |
| Tech stack | Go | Python |
| Docker Containers | 1 (app only) | 1 (app only) |
| Database | SQLite | none |
| Architecture | x86 + ARM | x86 + ARM |
Common questions
Does Borg need its own server?
No. A local directory works, and a remote repository only needs SSH plus Borg installed on the backup host. Borg 1.4, the stable release, has no S3 backend, so cloud storage means mounting it as a filesystem first; the 2.0 beta adds S3, B2 and rclone repositories.
Can Backrest and Borg share a repository?
No. Backrest manages Restic repositories and Borg writes its own archive format, so neither can open the other. They can live on the same machine, on separate disks, without either knowing about the other.
Which one sends alerts when a job fails?
Backrest, out of the box: its hooks post to Discord, Slack, Gotify, Shoutrrr or Healthchecks. Borg exits with a non-zero code, so with Borg alone the alert comes from cron or a wrapper script.
Does Backrest install Borg as well?
No. Backrest wraps Restic, using the Restic already installed if it is compatible and downloading one otherwise, so Borg is not involved at all. A Borg repository can only be read by Borg, and Borg 2.0 uses a new repository format that 1.x cannot open, so archives move across with borg transfer.
Sources: Backrest site and Borg docs.