Learn Proxmox Backup Server - Roadmap & Community

#Introduction

Episode 20 made PBS measurable. Now the question shifts direction: where is PBS going, and where can you take part? The technology you have learned over 20 episodes is not a dead object — it is continuously developed, and its developers involve the community. Episode 21 dissects the PBS roadmap and maps the community around it: forum, wiki, mailing list, documentation, all the way to contribution paths.

The analogy is like becoming a resident of a city under construction: there is a development plan map (roadmap), a city hall announcing progress (release notes & blog), and residents who meet, report, and help build (forum, mailing list, code).

#The PBS Roadmap

#S3 Object Storage as a Long-term Direction

The PBS 4.2 headline feature — S3 object storage (episodes 17 & 19) — is not a one-off experiment. It is a strategic direction that will keep living and maturing in the releases ahead. What to expect in the future along this direction:

• S3 feature maturity: more efficient sync, verify, and GC on buckets (including notification tuning and S3-specific thresholds already visible in 4.2).
• Dedup & performance improvements: refinements to chunking and the I/O path so dedup ratios rise and throughput improves with each release — Proxmox kernel 7.0 and ZFS 2.4 (episode 17) already provide the foundation.
• Deeper cloud integration: the "fast local + off-site to S3" pattern will become a first-class citizen, not a trick on the side.

#Release Model and Support Cycle

PBS follows the Debian release model: new major releases appear on top of new Debian stable. In 2026, PBS 4.2 sits on Debian 13.4 Trixie, and PBS 3 security support ends August 31, 2026 (episode 17) — meaning upgrading on time is part of "following the roadmap". Support information for each version can be checked at endoflife.date/proxmox-backup-server.

#Tracking the Roadmap: The Right Sources

• Official release notes: pbs.proxmox.com/docs/release-notes.html — the list of changes per release.
• The roadmap page on proxmox.com: a summary of Proxmox's overall development direction.
• Forum & bugzilla: the most requested feature requests often become the map of "what users want".
• Changelog/commits in the git repository: for those who want the earliest details, before release.

#The Community

#Proxmox.com: The Entry Point

• proxmox.com: the main site — products, downloads, press releases, and product documentation.
• pbs.proxmox.com/docs: official PBS documentation, the single always-updated source of technical truth (many episodes of this series are rooted there).
• wiki.proxmox.com: a wiki with community-experience-based guides, how-tos, and tutorials.

#The Forum: The Main Discussion Hub

forum.proxmox.com is the de facto Q&A center. Practices that get your thread answered fast:

• Provide your full version (proxmox-backup-manager versions), hardware, and relevant configuration.
• Attach the relevant task log / journalctl — the Proxmox forum cannot read minds.
• Search first; the problem you hit often already has a thread with a solution.

#Mailing List

Proxmox runs public mailing lists for development and users:

• pbs-devel: technical discussion and patches for PBS development — where to follow the technical direction before release.
• pve-devel: the counterpart for Proxmox VE, often relevant because PBS and PVE are integrated with each other (episode 4).
• The user mailing list (pve-user) for everyday usage discussions.

#Source Code & Contribution

PBS is open source (AGPLv3) software. The code can be explored at git.proxmox.com (proxmox-backup), with a public mirror on GitHub. Bugs are reported through bugzilla.proxmox.com — include the full version and logs. To influence the product direction, feature requests on the forum are the channel developers watch most.

#Enterprise Support

For production that needs guarantees, Proxmox offers a subscription (enterprise repo) with commercial support — a channel that gives SLA-backed answers. A healthy combination: the community for speed, the subscription for guarantees, and the official documentation as the final arbiter.

#Closing

Key takeaways:

• Roadmap: durable S3 object storage, dedup/performance improvements, and cloud integration.
• Releases follow Debian; PBS 3 security support ends August 31, 2026 — upgrade on time.
• Official documentation (pbs.proxmox.com/docs) is the source of truth; release notes for changes.
• Forum + mailing list (pbs-devel, pve-devel) = discussion and technical direction.
• Open source code (AGPLv3) on git.proxmox.com; bugs on bugzilla.proxmox.com.
• Contributions can be code, documentation, translations, testing, and good bug reports.

In episode 22 — the final episode — we will place PBS in the middle of a wider ecosystem: comparing it with Veeam, Bacula, restic/borg, and Velero, deciding when to choose which, summarizing the whole journey of episodes 0-21, and closing with a production checklist you can turn into a working document. See you at the finish line!