Skip to content

v0.9.0

Latest
Latest

Choose a tag to compare

View all tags
@wopner wopner released this 06 Nov 12:57
v0.9.0
This tag was signed with the committer’s verified signature.
wopner Tony D
SSH Key Fingerprint: HzEvo7r8x719x/XzBa5JDQFsFdsw79kNXIdaUt2a7a8
Verified
Learn about vigilant mode.
f5edb41

PBP 0.9.0: a clearer run summary

Every run's summary now accounts for each guest exactly once, in the counts line, in run.log and in the notification.

Upgrade both sides. The notification has two new sections that a 0.8 node helper refuses, so the PBP host and the Proxmox node must both run 0.9. Install 0.9.0 on each, then run the pbp node setup line that pbp setup prints (or pbp node install-templates on the node, as root) to install the new notification templates. Until both match, pbp check and every run stop at preflight. Configs need no change. See Upgrading.

What changed

  • Counts that add up, with a total. The summary starts with the number of guests, and every guest is in one count only:
    39 guests · ✅ 12 proven · ☑️ 11 previously proven · ⚠️ 2 error · ⚠️ 1 booted · ⏭️ 4 skipped · 🚫 8 excluded · 📄 1 template
    "Skipped" now means only guests not proofed for another reason, such as not enough memory or the run's deadline.
  • Excluded guests, with their status. A new 🚫 EXCLUDED BY CONFIGURATION section lists each excluded guest on its own line with the rule that excluded it and its last PBP verdict from any of its backups, so a guest excluded since its last proof doesn't drop out of sight:
    VM115: web02 (guests: 115) · last PROVEN 2026-10-12 02:14, or · never proofed.
  • Templates have their own 📄 TEMPLATES section.
  • Skipped guests one per line, with their name, like the other problem sections:
    VM104 db02 · backup Nov 5 02:00 · insufficient node memory.
  • run.log and pbp run use the same words: VM110 PREVIOUSLY PROVEN, VM115 EXCLUDED · guests: 115 · last PROVEN …, VM5000 TEMPLATE · not bootable, and pbp run ends with the same counts line.

Verdicts, severity, the notification's subject, backup notes and each guest's own log are unchanged.

Full details in the CHANGELOG.

Signed release. SHA256SUMS.sig is an SSH signature over SHA256SUMS by PBP's release signing key, fingerprint SHA256:HzEvo7r8x719x/XzBa5JDQFsFdsw79kNXIdaUt2a7a8 (ED25519), published in allowed_signers. Verify the download before installing:

curl -fsSLO https://raw.githubusercontent.com/Breadth-Security/PVE-Backup-Proofing/main/allowed_signers
ssh-keygen -Y verify -f allowed_signers -I pbp-release -n pbp-release -s SHA256SUMS.sig < SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missing

See Verifying a release.

Assets 8
Loading