Mr.PlanB Logo
    Open-Source Backup Ledger 2026
    Ledger
    Open-Source Backup Ledger 2026

    Barman: Open-Source Backup Ledger 2026

    Barman is EDB's centralised PostgreSQL backup manager and the backup engine behind CloudNativePG.

    Edition October 2, 20266 min read

    Part of the Open-Source Backup Ledger (edition 2026-10-02). How the scores work: methodology.

    Snapshot

    • Kind: Database backup tool
    • Licence: GPLv3
    • Backer: EnterpriseDB (EDB), which acquired 2ndQuadrant in 2020
    • Paid edition or support: EDB subscriptions and consulting
    • Latest release: 3.20.1, 2026-09-29
    • Next signal: 3.21; PostgreSQL 18 support; barman-cloud tuning for CloudNativePG
    • Archetype: Vendor-backed reference tool
    • Evidence grade: A. Release dates verified against GitHub where releases exist; the CVE identifier cited for 3.20.1 (CVE-2026-93853) was not independently verified.

    Scope of the scores: PostgreSQL only; compare it with other database tools.

    Scorecard

    DimensionScoreDirection
    Capability today62.2 / 100higher is better
    Momentum since end of 2022+1.2 pointshigher is better
    Credibility21.0 / 25higher is better
    Sustainability risk7.5 / 25lower is better
    Technical lock-in2.5 / 25lower is better
    Support and ecosystem14.5 / 20higher is better
    AI leverage1.0 / 20higher is better
    Ledger Index62.6 / 100balanced weights

    Capability by domain

    Scores 0 to 5 against fixed anchors; total is weighted to 100.

    Domain (weight)201620192022Today
    Virtual and physical servers (12)0.50.50.50.5
    Databases and applications (12)4444.5
    Recovery (14)3.53.544
    Cyber resilience (14)22.53.53.5
    Storage efficiency and targets (10)2.533.53.5
    Long-term retention and tape (6)3333
    Replication and DR (10)3.53.544
    Security and compliance (8)2.533.53.5
    New-platform support (VMware exit) (8)0.50.50.50.5
    Management at scale and automation (6)333.53.5
    Total / 10050.253.461.062.2

    Year by year: 2016: 50.2 · 2017: 50.2 · 2018: 50.2 · 2019: 53.4 · 2020: 53.4 · 2021: 53.4 · 2022: 61.0 · 2023: 61.0 · 2024: 62.2 · 2025: 62.2 · 2026: 62.2

    What moved the score

    YearDomainChangePointsTrigger
    2019Cyber resilience2 → 2.5+1.4barman-cloud client-side encryption
    2019Security and compliance2.5 → 3+0.8IAM roles
    2019Storage efficiency and targets2.5 → 3+1.0S3 via barman-cloud
    2022Cyber resilience2.5 → 3.5+2.8Object Lock support; GPG encryption
    2022Management at scale and automation3 → 3.5+0.6CloudNativePG automation, JSON status
    2022Recovery3.5 → 4+1.4Restore from cloud storage; standby bootstrap
    2022Replication and DR3.5 → 4+1.0Multi-region DR for CloudNativePG
    2022Security and compliance3 → 3.5+0.8Azure and GCP managed identities
    2022Storage efficiency and targets3 → 3.5+1.0S3, GCS, Azure; zstd
    2024Databases and applications4 → 4.5+1.23.12: block-level incremental for PostgreSQL 17

    Direction, 2023 to 2026

    Each item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

    DateItemThemeDriver
    2024-013.10: PostgreSQL 16 supportD2 Databases and applicationsU
    2024-113.12: block-level incremental backupD2 Databases and applicationsC
    2026-053.19.1: Azure managed identityD9 SecurityC
    2026-083.20: Python 3.12 minimumD12 Packaging and licensingU
    2026-093.20.1: security fixD9 SecurityC
    • Centre of gravity: Databases and applications (2), Security (2), Packaging and licensing (1)
    • Driver mix: Vision 0%, Customer need 60%, Market window 0%, Upstream 40%, Portfolio 0%

    Credibility: 21 / 25

    CriterionScoreBasis
    Cadence56 to 10 releases a year
    Roadmap transparency4Public issues and releases
    Say-do45 of 5 shipped; Azure managed identity took 16 months
    Velocity4Active
    Lifecycle stability4Stable; Python 3.12 minimum in 3.20

    Say-do record, 2023 to 2026: 5 items since 2023, all shipped; one took 16 months.

    Sustainability risk: 7.5 / 25 (lower is better)

    CriterionScoreBasis
    Maintainer concentration2.5Rotating EDB maintainers
    Backer health2Backed by EDB
    Licence-change risk1.5GPLv3
    Abandonment signs0.5Active
    Security response1Security fix released 9 days after advisory

    Project health: 3,247 stars; 22 open issues (median 290 days), 18 open PRs (152 days). 5 to 12 distinct authors a year.

    Technical lock-in: 2.5 / 25 (lower is better)

    CriterionScoreBasis
    Formats0.5Standard PostgreSQL data files
    Export path0.5Standard data files
    Stack coupling0.5Python tool
    Hardware / cloud coupling0Any POSIX or cloud target
    Skills and tooling coupling1PostgreSQL skills

    Support and ecosystem: 14.5 / 20

    CriterionScoreBasis
    Paid support4EDB support
    Consultants and partners3.5PostgreSQL consultancies
    Documentation3.5Good manual
    Community and packaging3.5In PGDG repositories; core of CloudNativePG backups

    AI leverage: 1 / 20

    StrandTodayLatest step
    AI for protection / protecting AI0none
    AI platform stack0none
    AI-assisted operations0none
    Agent openness12016: JSON status output

    No AI features.

    Reading

    Barman is EDB's centralised PostgreSQL backup manager and the backup engine behind CloudNativePG. It matches pgBackRest on the essentials, with a server-pulls model that suits central backup teams, and has a broader set of maintainers.

    Open questions and evidence caveats

    • The CVE number in the research file should be checked before it is cited.

    Related reading

    More from Open-Source Backup Ledger 2026