BARMAN-VERIFY-BACKUP(1)

📦
version 3.20.1 · 7 versions
, in epel 10, fedora 43, fedora 44

💖 BARMAN-VERIFY-BACKUP 💖

okay so bestie, welcome to the barman-verify-backup page — this is one of the Barman Sub-Commands, and it's literally the vibe check for your backups. no cap.

✨ SYNOPSIS ✨

verify-backup
    [ { -h | --help } ]
    SERVER_NAME BACKUP_ID

🌸 DESCRIPTION 🌸

So what does this icon do? It runs pg_verifybackup on a backup manifest file — and heads up, that's only a thing since Postgres version 13, so if you're on something older... 🙈

For rsync backups, you can totally use this after you've created a manifest file with the generate-manifest command. It requires pg_verifybackup to be installed on the backup server, periodt. Oh and also — you can use a shortcut instead of BACKUP_ID (more on that below, keep scrolling 💅).

Starting with Postgres 18, tar-format backups taken with the postgres backup method can also be verified — including ones compressed with gzip, lz4 or zstd. iconic.

⚠️ but wait — verifying tar or compressed backups requires pg_verifybackup from Postgres 18 or newer to be available on the backup server. if it's not, the command will straight up fail with an error. no soft launch, just failure. 😭
💀 and encrypted backups? not supported by this command. at all. don't try it.

🎀 PARAMETERS 🎀

  • SERVER_NAME — the name of the server in barman node. that's your girl's name in the group chat, basically.
  • BACKUP_ID — the id of the backup in the barman catalog. yes, the actual backup's id. keep up bestie 🫶
  • -h / --help — shows a help message and exits. it gives you all the info about how to use the command, which is lowkey very helpful when you're lost.

🌈 SHORTCUTS 🌈

For some commands, instead of using the timestamp backup ID, you can use these shortcuts (aka aliases) to identify a backup for a given server. it's giving convenience, honestly:

  • first / oldest — the oldest available backup for the server, in chronological order.
  • last / latest — the most recent available backup for the server, in chronological order.
  • last-full / latest-full — the most recent full backup taken with methods rsync or postgres.
  • last-failed — the most recent backup that failed, in chronological order. (we don't talk about her 💀)

👑 Author

EnterpriseDB

© Copyright EnterpriseDB UK Limited 2011-2026

and that's the whole page, bestie!! this was Barman 3.20, dated Sep 29, 2026, and yeah the manual name is literally right up there in the title: BARMAN-VERIFY-BACKUP(1) 🦋✨ go verify those backups, you absolute main character 💅

📦 where this page comes from