Backrest vs borgmatic

Editor take

Choose Backrest for a browser that browses and restores snapshots, and for schedules it runs itself. Choose borgmatic for database dumps before each archive and for one YAML file you can version.

Editor

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

  • Snapshots in a browserBrowse every snapshot and restore a single file or folder from the dashboard; borgmatic restores from the command line with borgmatic extract.1
  • Schedules it runs itselfPlans carry their own cron schedule and retention; borgmatic is a one-shot command, so cron or a systemd timer has to call it.2

borgmatic

Where borgmatic is stronger

  • Database dumps before the archiveDumps Postgres, MySQL, MariaDB, MongoDB, SQLite, InfluxDB and OpenLDAP first, so the archive holds a clean copy; Backrest expects a hook you write.3
  • One YAML file for everythingRepositories, sources, retention and checks live in one file you can version and copy to a new host; Backrest keeps its plans in the app.4

Backrest vs borgmatic: 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
PriceFreeFree
LicenceGPL-3.0GPL-3.0
Concurrent backupsSequential / lockedSequential / locked
Storage supportLocal, SFTP, S3, B2, rcloneLocal, SSH
NotificationsDiscord, Slack, Gotify, Shoutrrr, HealthchecksApprise, Healthchecks, ntfy, Pushover, Uptime Kuma, Zabbix
DeduplicationYes (per repository)Yes (per repository)
Web UIYes–
DockerYesYes
Linux packageYesYes
WindowsYes–
macOSYesYes
Tech stackGoPython
Docker Containers1 (app only)1 (app only)
DatabaseSQLitenone
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Backrest site and borgmatic docs.

Updated