Learn Borg Backup - Ecosystem, Alternatives & Final Reflections

#Introduction

This is the last of 23 episodes. You have mastered Borg from zero to production — and now it is time to look at it from above: where Borg stands among other tools, when to choose which, and how to close this journey with a checklist you can use right away. A good engineer is not just skilled at one tool; they know when that tool is the right one.

#Tool Comparison

#Borg vs Restic vs Others

+------------------+---------------------------------------+------------------------------+
| Tool             | Main strength                         | When to choose               |
+------------------+---------------------------------------+------------------------------+
| Borg (1.4.5)     | dedup+compression+encryption, local/  | simple local/SSH backups     |
|                  | SSH, archive mount (FUSE), append-only| with aggressive compression  |
+------------------+---------------------------------------+------------------------------+
| Restic           | Go, many cloud/object backends        | when you need S3/object      |
|                  | (S3, Backblaze, etc), AES encryption, | storage & multi-platform     |
|                  | multi-platform binary                 |                              |
+------------------+---------------------------------------+------------------------------+
| Borgmatic        | YAML config wrapper on top of Borg    | Borg automation & policy     |
+------------------+---------------------------------------+------------------------------+
| rsync / tar      | simple, no dedup                      | periodic synchronization, not|
|                  |                                       | history backups              |
+------------------+---------------------------------------+------------------------------+
| Proxmox Backup   | chunk dedup + VM/CT integration,      | VM/CT backups in a Proxmox   |
| Server (PBS)     | incremental forever                   | cluster                      |
+------------------+---------------------------------------+------------------------------+
| Bacula / Veeam   | enterprise suite, central console     | large enterprises, compliance|
|                  |                                       | & complex orchestration      |
+------------------+---------------------------------------+------------------------------+

The practical reading:

• Borg: the primary choice for server, desktop, and VM backups over local/SSH with excellent dedup and compression — exactly what we built throughout this series.
• Restic: its advantage is object storage backends (S3, Backblaze B2) and the portability of the Go binary. Suitable when the main target is cloud storage rather than SSH.
• Borgmatic: not an alternative, but an enhancer of Borg — YAML configuration, hooks, monitoring. If you use Borg in production, borgmatic is almost mandatory.
• rsync/tar: no dedup and not history backups; suitable for synchronization, not recovery points.
• PBS: chunk-level dedup with native Proxmox VM/CT integration — the natural choice when your infrastructure is Proxmox.
• Bacula/Veeam: suites with consoles, orchestration, and compliance — their value shows in large organizations with many platforms.

#When to Choose

• Borg when: local/SSH repos, a need for aggressive compression, full control via CLI.
• Restic when: you need S3/object storage, multi-platform, or a cloud-native ecosystem.
• PBS when: a Proxmox environment with VM/CT workloads.
• Veeam/Bacula when: large enterprises with compliance requirements and orchestration needs.
• The principle: start with the simplest tool that meets your needs, and scale up only for a real reason.

#Recap of the 22-Episode Journey

Across six phases we built layered understanding:

1. Fundamentals (0-2): prerequisite skills, history & philosophy, repo/archive/chunker architecture.
2. Basic operations (3-7): init, create, extract, compression, encryption & keys.
3. Workload & data (8-12): prune/compact, borgmatic, databases, remote SSH, check.
4. Security (13-15): append-only, multi-host hardening, CVE & security releases.
5. Advanced (16-18): troubleshooting, Borg 1.4.5 vs 2.0, performance & large datasets.
6. Ecosystem & production (19-22): BorgWeb & tools, monitoring/alerting, roadmap, reflections.

It all comes down to one principle: a backup is a process, not an event — and it is only worth anything if it can be restored.

#The Production Checklist

[x] Encrypted repository (repokey-blake2 / keyfile-blake2)
[x] Append-only mode enabled on the server side (borg serve --append-only)
[x] borgmatic automates create → prune → compact → check
[x] Retention policy documented per RPO/RTO
[x] Routine borg check (monthly) + check --verify-data (yearly)
[x] Passphrase/keyfile safe in a password manager + key backup
[x] Scheduled restore drills (monthly/quarterly) with documented results
[x] Monitoring: failure alert (on_error) + lateness alert (staleness)
[x] Off-site copy on a different host/location
[x] Borg version watched and upgraded on security releases

#Official Learning Resources

• Documentation: borgbackup.readthedocs.io — the primary reference, including the 1.4.5 changelog.
• Website: borgbackup.org.
• Code & releases: github.com/borgbackup/borg (releases, issues, PRs).
• Borgmatic: borgmatic.readthedocs.io.
• Community: the IRC/Matrix channel #borgbackup.

#Closing

• Borg excels at dedup + compression + encryption for local/SSH repos; Restic for cloud/object; PBS for VM/CT; Bacula/Veeam for enterprise.
• Borgmatic is the essential companion for Borg automation in production.
• The production checklist is ready to use: encryption, append-only, automation, check, keys, restore drills, monitoring, off-site.
• Official learning resources: readthedocs, borgbackup.org, GitHub, and the community.
• A good backup is one that dares to be restore-tested — keep testing, keep improving.

The Learn Borg Backup series is complete — 23 episodes, one solid foundation. From the first borg init in episode 3 to this production checklist, you now have a skill few teams have: backups that are deduplicated, secure, automated, and proven recoverable. Now close your laptop, run your restore drill, and make sure the data you care about is truly safe. Congratulations, and see you in the next series!