BorgBackup
Deduplicating encrypted backups with strong ops pedigree
Review status: Evaluated. Read the evidence and pilot limits below before choosing.
Official Website · Source Code
oss-osi-approved full guideOverview
BorgBackup is a mature deduplicating backup tool. Operators with Linux skills use it for efficient on-site and off-site backups.
At a glance
| Field | Value |
|---|---|
| Categories | backup-recovery |
| Deployment | self-hosted |
| License class | oss-osi-approved (BSD-3-Clause) |
| Cost model | free-self-hosted |
| Implementation difficulty | moderate |
| Maintenance burden | medium |
| Maturity | stable |
| Freshness status | partially-verified (2026-07-17) |
| Completeness | editorially-reviewed |
| Confidence | medium |
| Directory tier | evaluated |
Cost reality
Free software; storage targets cost money.
Pricing and free-tier limits change frequently; re-check official pricing before budget decisions.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Efficient encrypted backups
- Space-saving dedupe
Human oversight still needed
- Passphrase management
- Remote repo availability
Manual process this can replace
perform-backup-restore-tests
- Relationship: infrastructure
- Automation level: partially automated
- Manual process this can replace: Re-copying unchanged service data for every backup and manually locating files in dated backup folders during a restore test.
- Tasks it can reduce: Creates deduplicated encrypted archives and provides archive listing, checking, and extraction commands for a controlled restore drill.
- Role it assists: it-security-administrator
- What still requires a person: Prepare an application-consistent source, control keys and restored personal data, select the recovery point, and have the business owner verify restored usability and integrity.
- What happens if it fails: A successful archive job can still produce unusable or incomplete recovery data; failed key custody or unsafe restoration can cause permanent loss or expose personal data.
- How to measure the pilot: One representative service restores on a clean isolated host within the measured objective and passes every owner-approved integrity check.
- Confidence: medium
Data held
-
encrypted archives
-
Personal data: yes
-
Payment data: no / not primary
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Evaluate export formats and API completeness before deep customization. |
| Security | Apply updates promptly; restrict admin access; enable TLS. |
| Compliance | Operator remains responsible for privacy and local regulatory obligations. |
| Licensing | Confirm license fits commercial coworking use. |
| Operational | Plan backups, monitoring, and a restore drill before production use. |
Coworking fit
Roles: technical-operator
Workflows: backup-restore-drill
Problems: disaster-recovery, self-host-for-data-control
Smallest useful experiment
Initialize a repo, back up /var/lib for one service, restore a single file successfully.
Initial planning estimate (unverified): 1–3 days
Links
Implementation guide
See the human-written implementation guide.
Verification
- Status:
partially-verified - Completeness:
editorially-reviewed - Confidence:
medium - Tier:
evaluated - Last reviewed:
2026-07-17 - Sources:
Seed entry compiled from official project sites and repositories. Re-verify pricing, license text, and feature claims before production decisions. Star counts and free-tier numeric limits intentionally omitted unless verified at review time.