BARMAN-SYNC-BACKUP(1)

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

✨ barman-sync-backup 💖 (a page from the Barman manual, section 1, bestie)

okay so hi!! 🫶 this is the manual page for barman-sync-backup, and yes it lives in the Barman docs, and yes we're gonna get through it together. grab a snack. 🍓

🌸 NAME 🌸

barman-sync-backup — Barman Sub-Commands ✨

🎀 SYNOPSIS 🎀

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

like. that's the whole shape of it. SERVER_NAME then BACKUP_ID, and optionally a little -h or --help if you're feeling curious. 💅

🦋 DESCRIPTION 🦋

okay so what does this actually do? This command synchronizes a passive node with its primary by copying all files from a backup that's present on the server node. 🫶 that's the whole vibe — primary has the backup, passive wants it, this command makes it happen.

lowkey important: it's available only for passive nodes. so if you're not on a passive node, this is not your moment bestie. 😭

it uses the primary_ssh_command option to establish a secure connection with the primary node. 🔐 no cap, that's the mechanism.

and the cute part — you can use a shortcut instead of BACKUP_ID. so you don't have to type out a whole timestamp if you don't want to. (scroll down, I got you. ⬇️)

👑 PARAMETERS 👑

  • SERVER_NAME — Name of the server in barman node.
  • BACKUP_ID — Id of the backup in barman catalog. it's giving "your backup's official government name" fr fr.
  • -h / --help — Show a help message and exit. Provides information about command usage. it's literally just there to help you, that's it, that's the whole job. 💖

🌈 SHORTCUTS 🌈

so for some commands, instead of using the timestamp backup ID, you can use the following shortcuts (aka aliases) to identify a backup for a given server. this is the part where you go "oh wait that's so much easier" ✨

  • first / oldest — Oldest available backup for the server, in chronological order. ⏳
  • last / latest — Most recent available backup for the server, in chronological order. 🕐
  • last-full / latest-full — Most recent full backup taken with methods rsync or postgres. 🔥
  • last-failed — Most recent backup that failed, in chronological order. 💀 (we don't talk about this one but it exists and it's useful, periodt.)

💜 Author 💜

EnterpriseDB

© Copyright EnterpriseDB UK Limited 2011-2026

okay that's the whole page!! 🎀 this was version 3.20, dated Sep 29, 2026, and it's the BARMAN-SYNC-BACKUP(1) page from the Barman manual. go sync something, bestie — you got this. 💖✨🦋

📦 where this page comes from