Proxmox Backup Server (PBS)
The Instructor's Perspective
In the Army, we had “recovery plans.” A backup you haven’t tested is just a “manageable mess” in waiting. PBS is your enterprise-class solution for ensuring that when (not if) a server fails, you’re back in the fight within minutes. It’s an essential part of your “recovery discipline.”
Why use it?
- Incremental Backups: Only the changes (deltas) are transferred, making backups near-instant.
- Deduplication: Save massive amounts of space on your NAS or backup storage.
- Durable Encryption: Your backups are encrypted before they ever leave the hypervisor.
- Verification: Automatically checks the integrity of your backups periodically.
Backup Reliability (The PACE Plan)
Recovery Discipline
P (Primary): Proxmox Backup Server (Dedicated LXC or VM on local storage). A (Alternate): Automated offsite synchronization to a secondary PBS or local NAS via RSync. C (Contingency): Proxmox “VZDump” backups (Standard Proxmox backups) to a separate network share. E (Emergency): Critical data (e.g., Vaultwarden DB) copied to an encrypted physical USB drive.
Standard Operating Procedure (SOP): Managing Your Backups
- Define Your Scope: Decide what must be backed up every night and what can wait for a weekly job.
- Configure Storage: Set up a dedicated data store for your backups. SSDs are highly recommended for performance.
- Automate: Use the Proxmox VE interface to schedule daily, incremental backups for every critical VM and container.
- Prune and Verify: Set a retention policy (e.g., keep 7 days, 4 weeks, 6 months) and enable periodic verification.
- Test a Restore: Once a month, restore a non-critical VM to ensure your “recovery discipline” is sound.
Check for Understanding
- Why is it important to test your restore process? (Hint: Think about “human error”).
- How does “Deduplication” save you money on storage hardware?
Related: index, The Stack, SOP - Updating the Home Lab