Learn Proxmox Backup Server (PBS) — the open source enterprise backup solution for VMs, containers, and physical hosts — from installation to production-grade: prerequisite skills & environment setup, background history & why you need it, core concepts & key architecture, installation & initial configuration, VM/CT backup from Proxmox VE, VM/CT restore & file-level recovery, deduplication & garbage collection, client-side encryption, retention & prune policy, verify & integrity check, remote sync & off-site backup, physical host & container backup, ACL user & remote access, network isolation & firewall, repository security & anti-ransomware, backup storage ZFS ext4 & SMB/NFS, troubleshooting & recovery, PBS 4.2 & the latest features, scaling many datastores & sync architecture, Veeam Bacula & cloud ecosystem integration, monitoring & performance, roadmap & community, all the way to the alternative ecosystem & final reflection with a total of 23 episodes.
Before touching Proxmox Backup Server, you need to master Linux administration (network, storage, services), understand the backup concepts as well as Proxmox VE basics, and prepare the right software and hardware: PBS 4.2, ZFS/LVM/NFS storage, and Proxmox VE 8.x/9.x clients. In this episode you will also verify that your entire environment is ready for backup.

This episode traces the origins of Proxmox Backup Server: a project started by Proxmox in 2018 with the first stable 1.0 release in 2020 as the backup backbone of the Proxmox VE ecosystem. You will also understand why PBS is needed — per-chunk deduplication, client-side encryption, instant restore, native integration, off-site sync, and its role as a Veeam/Bacula target.

This episode dissects the Proxmox Backup Server architecture: the datastore as the home of chunks, content-defined chunking for dedup across backups, and backup groups and snapshots per VM/CT/host. You will also understand the supporting components — the proxmox-backup server, the web UI on port 8007, the proxmox-backup-client CLI, and the API — plus its integration with the PVE datacenter.

This episode guides you through installing Proxmox Backup Server 4.2 via the ISO installer or the apt repository, disk and ZFS selection, and network and hostname configuration. You will also create the first datastore with GC and verify schedules, then understand the user realm options — PAM, AD/LDAP, and Proxmox VE — before adding the first user.

This episode guides you through integrating PBS into the Proxmox VE datacenter: adding PBS as storage via Datacenter → Storage with the server, datastore, and certificate fingerprint. You will also choose the backup mode (guest agent, snapshot, suspend, stop), schedule regular backups from PVE, and verify that snapshots appear in PBS.

This episode covers the most important side of backup — recovery. You will fully restore VMs/CTs to the original PVE or a different node, use the file restore feature to grab individual files without a full restore, and perform file recovery and boot testing of restored results to ensure your RTO is met.

This episode dissects PBS efficiency: content-defined chunking that produces dedup across backups and VMs, and how to read the dedup metrics in a datastore. You will also understand the prune (retention) then garbage collection flow to delete unused chunks, and schedule GC so your storage does not balloon.

This episode secures backup data with client-side encryption: creating a base64 key on the client side, pointing it to PVE/PBS backup tasks, and verifying that the server only stores unreadable ciphertext. You will also learn proper key management — because without the key, restore is impossible.

This episode manages the snapshot lifecycle: the prune policy with keep-last, keep-daily, keep-weekly, and keep-monthly per backup group, and how sync jobs maintain retention on the remote side. You will learn to align retention with RPO/RTO targets and verify prune results so the datastore stays healthy.

This episode ensures stored snapshots do not silently corrupt: scheduling a verify job that re-reads and validates every chunk's checksum, using the verify-new option for new snapshots, and performing integrity audits via task logs and datastore checks. A backup that corrupts undetected is a disaster waiting to happen.
