Researched comparison

Best PostgreSQL Backup Software for Small Teams

Tierlyn may earn a fee from some links on this page, and some placements are paid and labelled. Neither one decides the order. See our disclosure.

The short answer

pgBackRest is the top pick for small teams running PostgreSQL on their own servers. It is free and open source, and it supports point-in-time recovery, parallel backup and restore, compression, encryption, and retention policies without a licence fee. It needs command-line setup, so teams wanting a graphical console should consider Barman, Veeam, or Commvault instead.

Key takeaways

  • pgBackRest is the strongest no-cost starting point for self-managed PostgreSQL, with point-in-time recovery and parallel backup and restore.
  • Barman is a sound free choice when a team wants a dedicated backup server and a clear retention policy for physical backups.
  • pg_dump and pg_basebackup cover simple exports and base backups at no cost, but they need extra scripting for retention, remote storage, and point-in-time recovery.
  • Veeam, Commvault, Rubrik, Cohesity, and EDB suit teams that need central management, wider platform cover, or commercial support, and most of them publish no list price.
  • Test a restore before you rely on any backup, because a backup that has never been restored is only a hope, not a recovery plan.
Contents

Tier labels are an editorial grouping, not a number and not a rating out of any total. S means a top tier pick for most readers. A means a strong choice with a clear strength. B means a solid option for a specific need.

S A B

Comparison at a glance

Comparison

How these compare
ToolBest forPrice rangeFree plan
pgBackRestSelf-managed PostgreSQL with point-in-time recovery$0, free and open sourceYes
BarmanDedicated backup server for PostgreSQL$0, free and open sourceYes
pg_dump and pg_basebackupSimple exports and base backups$0, included with PostgreSQLYes
Veeam Backup and ReplicationCentral backup for mixed environmentsquote onlyYes, Community Edition free up to 10 workloads
Commvault CloudCloud database backup with central policy$90 per TB per monthNo
Rubrik Security CloudCentral data protection with threat detectionquote onlyNo
Cohesity DataProtectCentral backup across on-premises and cloudquote onlyNo
EDB Backup and Recovery Tool (BART)Existing EDB Postgres estatesquote onlyNo

Ranked by tier

1

self-managed PostgreSQL with point-in-time recovery

pgBackRest

pgBackRest is the standard open-source backup tool for PostgreSQL on a server a team controls. It takes full, differential, and incremental backups, archives write-ahead log files for point-in-time recovery, and supports parallel backup and restore, which matters when a database grows past a few tens of gigabytes. It also supports compression, encryption, retention policies, and backup to local disk, network storage, or object storage such as S3.

The tool does not cover everything. It has no graphical interface and no built-in scheduler, so the team must write and monitor the schedule itself. It needs direct access to the PostgreSQL server and data directory, which means it does not work on managed services such as Amazon RDS, Supabase, or Neon, where the provider controls the underlying files. For teams that accept those limits, pgBackRest gives the most complete PostgreSQL backup feature set at no licence cost.

Pros:

  • point-in-time recovery with WAL archiving
  • parallel backup and restore, compression, and encryption

Cons:

  • command-line only, with no built-in scheduler or graphical interface
  • needs direct access to the server and data directory, so it does not work on managed services such as RDS, Supabase, or Neon

Price: $0, free and open source

Free plan: Yes

Website: pgbackrest.org

Best for: self-managed PostgreSQL with point-in-time recovery

2

dedicated backup server for PostgreSQL

Barman

Barman, which stands for Backup and Recovery Manager, is a free open-source tool from 2ndQuadrant, now part of EDB, for taking physical backups of PostgreSQL. It runs on a dedicated Linux backup server, connects to the database over streaming replication, and keeps a catalogue of base backups and WAL files with named retention policies. Commands such as barman backup, barman list-backup, and barman recover give a small team a repeatable routine, and Barman can copy backups to a remote store or to object storage.

Barman does not cover logical backup. It is physical-only and never uses pg_dump, so it cannot export a single table or a single schema on its own. It requires a dedicated Linux backup server, and it needs a superuser or replication connection and SSH in some modes, which adds setup work and a second machine to maintain. It also does no test restore by itself, so the team must schedule a restore test and check the result.

Pros:

  • clear retention and recovery commands for physical backups
  • supports remote backup over streaming replication

Cons:

  • requires a dedicated Linux backup server
  • needs a superuser or replication connection and SSH in some modes, is physical-only and never uses pg_dump, and does no test restore

Price: $0, free and open source

Free plan: Yes

Website: pgbarman.org

Best for: dedicated backup server for PostgreSQL

3

simple exports and base backups

pg_dump and pg_basebackup

pg_dump and pg_basebackup ship with PostgreSQL, so every team already has them. pg_dump exports a database, a schema, or a single table as SQL or as a custom-format archive, which is handy for moving data between environments and for taking a logical copy before a major change. pg_basebackup takes a physical base backup of a whole cluster, which is the starting point for a replica or for a restore combined with WAL archiving.

The limits are real and they shape when these tools are enough. pg_dump has no point-in-time recovery and restores slowly on large databases because indexes rebuild during the restore, so a multi-hundred-gigabyte database can take hours to bring back. pg_basebackup has no retention management, no remote storage abstraction, and no parallel restore, and it needs external WAL archiving for point-in-time recovery. Neither tool schedules itself, checks itself, or alerts the team when a backup fails.

Pros:

  • included with every PostgreSQL install, with no extra download
  • pg_dump exports single databases, schemas, or tables in a portable form

Cons:

  • pg_dump has no point-in-time recovery and restores slowly on large databases because indexes rebuild
  • pg_basebackup has no retention management, no remote storage abstraction, and no parallel restore, and needs external WAL archiving for point-in-time recovery

Price: $0, included with PostgreSQL

Free plan: Yes

Website: postgresql.org

Best for: simple exports and base backups

4

central backup for mixed environments

Veeam Backup and Replication

Veeam Backup and Replication is a broad data protection platform that covers virtual machines, physical servers, cloud workloads, and applications, including PostgreSQL in many deployments. A small team that already runs Veeam for other systems can add PostgreSQL backup to the same console, repository, and retention rules, rather than running a separate PostgreSQL-only tool. Its Community Edition is free for up to 10 workloads. Check current price, because Veeam publishes no dollar list price for the commercial editions.

Veeam does not cover every PostgreSQL need in the same way a native tool does, and its pricing needs a direct quote. Storage is bought separately, so the total cost depends on the repository a team chooses. Licences are sold in 10-workload packs, 5 for Essentials, on annual billing only, which can make a very small estate pay for more capacity than it uses.

Pros:

  • central console for virtual, physical, and cloud workloads
  • Community Edition covers up to 10 workloads at no licence cost

Cons:

  • storage is bought separately
  • licences are sold in 10-workload packs, 5 for Essentials, on annual billing only

Price: quote only

Free plan: Yes, Community Edition free up to 10 workloads

Website: veeam.com

Best for: central backup for mixed environments

5

cloud database backup with central policy

Commvault Cloud

Commvault Cloud is a data protection service that covers databases, virtual machines, cloud workloads, and file data from one console. For PostgreSQL, it offers database backup as part of its Cloud SaaS edition, priced at $90 per TB per month for database backup, which gives a small team a clear starting figure to model against the size of its databases. Central policy, scheduling, retention, and reporting sit in one place.

The limits are worth noting before a team commits. Self-managed licensing is quote only on front-end terabytes, so the $90 per TB figure applies to the Cloud SaaS database backup edition and not to every Commvault deployment. Application-consistent database protection is agent-based, which means the team installs and maintains an agent on the database host and checks that it stays current.

Pros:

  • central policy and reporting across many workloads
  • database backup priced per TB in the Cloud SaaS edition

Cons:

  • self-managed licensing is quote only on front-end terabytes
  • application-consistent database protection is agent-based

Price: $90 per TB per month

Free plan: No

Website: commvault.com

Best for: cloud database backup with central policy

6

central data protection with threat detection

Rubrik Security Cloud

Rubrik Security Cloud is a data protection platform that covers cloud workloads, virtual machines, physical servers, databases, and software-as-a-service data from a single console. It applies policy by workload, automates backup and retention, and adds security features such as immutable backups, anomaly detection, and threat monitoring, which help a team spot ransomware activity and recover clean data. Check current price, because Rubrik publishes no list price for its editions.

Rubrik does not cover every deployment in the same way. On-premises deployment needs Rubrik cluster or appliance hardware, which adds cost and a hardware decision that a cloud-only team may not want. Threat monitoring and threat hunting are in the higher Enterprise Edition, so a team that buys a lower edition does not get the full security feature set. Rubrik also needs a direct quote for pricing, so a small team cannot model its cost from a public price list.

Pros:

  • central policy across cloud, virtual, and physical data
  • built-in threat monitoring and anomaly detection in higher editions

Cons:

  • on-premises deployment needs Rubrik cluster or appliance hardware
  • threat monitoring and threat hunting are in the higher Enterprise Edition

Price: quote only

Free plan: No

Website: rubrik.com

Best for: central data protection with threat detection

7

central backup across on-premises and cloud

Cohesity DataProtect

Cohesity DataProtect is a data protection platform that covers virtual machines, physical servers, databases, cloud workloads, and file data, with backup, recovery, and data management in one system. A team can run it on premises as a cluster, or use DataProtect as a Service and let Cohesity run the backup infrastructure, which removes the need to buy and maintain backup hardware. Check current price, because Cohesity publishes no list price for DataProtect.

The limits follow from the platform model. Self-managed deployment runs as clusters on Cohesity or partner hardware, so an on-premises team must plan for that hardware and its sizing. DataProtect as a Service pricing comes from a Cohesity sales quote, so a team cannot model its cost from a public price list and must ask for a figure based on its data size and retention needs.

Pros:

  • one platform for backup, recovery, and data management
  • DataProtect as a Service removes the need to run backup hardware

Cons:

  • self-managed deployment runs as clusters on Cohesity or partner hardware
  • DataProtect as a Service pricing comes from a Cohesity sales quote

Price: quote only

Free plan: No

Website: cohesity.com

Best for: central backup across on-premises and cloud

8

existing EDB Postgres estates

EDB Backup and Recovery Tool (BART)

EDB Backup and Recovery Tool, known as BART, is a backup and recovery tool built for EDB Postgres. It takes full and incremental physical backups, manages WAL archiving for point-in-time recovery, and gives teams running EDB Postgres a backup routine that fits that platform. Check current price, because EDB publishes no list price for BART as a separate product, and pricing usually forms part of an EDB Postgres subscription.

BART does not cover the future in the way a team might expect. EDB states BART will continue to be supported but will no longer receive new feature updates, and EDB now lists Barman and pgBackRest as its officially supported backup tooling. That means a new team choosing a backup tool today should weigh BART against Barman and pgBackRest, which receive active development and new features.

Pros:

  • built for EDB Postgres, with backup and recovery commands for that platform
  • suited to teams already running EDB software

Cons:

  • EDB states BART will continue to be supported but will no longer receive new feature updates
  • EDB now lists Barman and pgBackRest as its officially supported backup tooling

Price: quote only

Free plan: No

Website: enterprisedb.com

Best for: existing EDB Postgres estates

How we choose

How we choose

We compared vendor pricing pages, product documentation, and feature pages for each tool, and we checked what each tool covers and what it does not cover. We gave weight to PostgreSQL-specific features such as point-in-time recovery, parallel backup and restore, WAL archiving, and retention policy. We did not claim hands-on testing, and we did not use customer counts, awards, or test results. Where a vendor publishes no list price, we wrote quote only and asked the reader to check current price with the vendor.

Our full method

Buyers guide

Check where the backup will live, how long it will be kept, and how a restore will be tested. A backup that stays on the same server as the database does not protect against a server failure, so keep at least one copy off site or in object storage. Check the recovery point objective and the recovery time objective in plain numbers: how much data can the team lose, in minutes, and how long can a restore take, in hours. Check whether the tool supports point-in-time recovery, and whether it needs WAL archiving, a dedicated server, or an agent on the database host. Check the restore test: run it on a copy, time it, and record the result.

Team size and budgetBest starting choiceWhat to budget for
1 to 3 people, no budgetpgBackRest or BarmanStorage, about 2 times the database size for full plus WAL copies, and time to write and test scripts
1 to 3 people, small budgetpgBackRest plus pg_dump exportsStorage and a test server for restore checks, with no licence fee
4 to 10 people, mixed estateVeeam Community Edition, then a commercial quoteStorage bought separately, and licences in 10-workload packs, 5 for Essentials
4 to 10 people, cloud-firstCommvault Cloud at $90 per TB per monthMonthly cost per TB, plus agent time on each database host
10 or more people, central policyRubrik, Cohesity, or Commvault, by quoteHardware or service fees by quote, plus time for policy and restore testing

Frequently asked questions

Does pgBackRest work with managed PostgreSQL services?

No, pgBackRest does not work with managed services such as Amazon RDS, Supabase, or Neon. It needs direct access to the PostgreSQL server and data directory, which managed providers do not give to customers. Teams on managed services should use the backup and point-in-time recovery features that the provider supplies, and they should test a restore from the provider backup.

How often should a small team test a PostgreSQL restore?

A small team should test a restore at least once a month, and after every major change to the database, the backup script, or the storage. A monthly test catches a broken script, a full disk, or a missing WAL archive before it matters. Record the time the restore took and the data that came back, and keep that record with the backup log.

What is point-in-time recovery, and why does it matter?

Point-in-time recovery lets a team restore a database to a chosen moment, rather than only to the last full backup. It uses a base backup plus write-ahead log files to replay changes up to that moment. It matters after a bad migration or an accidental delete, because the team can recover to just before the error.

Is pg_dump enough for a production PostgreSQL database?

pg_dump can be enough for a small database with a simple restore need, but it has clear limits. It has no point-in-time recovery, and it restores slowly on large databases because indexes rebuild during the restore. For production use, pair pg_dump with a physical backup tool such as pgBackRest or Barman, and test the restore time on a copy before relying on it.

How much storage should a team keep for PostgreSQL backups?

A team should plan for at least 2 times the size of its largest database, and more if it keeps several full backups or a long WAL archive. Measure the real backup size after the first full backup, then set retention and storage alerts based on that number.

When should a team choose a commercial backup platform over a free tool?

A team should choose a commercial platform when it needs a central console, central policy, and reporting across many workloads, or when it needs commercial support and a single vendor to call. Free tools such as pgBackRest and Barman cover PostgreSQL well, but they need scripting, monitoring, and restore testing by the team.

Sources

About the team

Tierlyn Editorial Team

Tierlyn sorts security, identity and backup tools into tiers instead of a single ranked list, because a top pick for a five-person startup can sit lower for a regulated enterprise. Every tier states the team size and risk level it was built for, and lists the price we saw on the vendor page with the date attached. We update a tier the moment a vendor changes a plan or drops a feature we relied on.

Related guides