Proxmox Backup Server can manage backups efficiently and check their technical condition. Reliable operation nevertheless requires several tasks to work together. In particular, verification, retention, storage cleanup and an actual restore test answer different questions.
A successful run is the starting point
The backup job must cover the intended systems and required states. Checks also establish whether errors and missed runs are noticed. A green last run can hide the fact that a new VM has not yet been included in the plan.
Scope and frequency follow the acceptable data loss and the rate of change in the applications. The chosen storage and access architecture is also assessed. If the original system fails, the backup data and the keys needed to use it must remain accessible.
Verification checks integrity, not the business workflow
PBS provides scheduled integrity checks for backup sets. Previously checked backups can be verified again. This matters because the condition of stored data can change over time.
A successful verification result is not application acceptance from a business perspective. On its own, it does not establish that sign-in, the database and interfaces will work as required after restoration. A suitable recovery test with a responsible person is planned for that purpose.
Distinguish pruning from garbage collection
Pruning determines which backup snapshots remain under the selected retention rules. The manufacturer’s documentation distinguishes removing snapshot metadata from subsequently reclaiming unused data chunks through garbage collection. Space is therefore not necessarily freed immediately after a retention rule changes.
The rules are checked using an understandable example: which daily, weekly or older snapshots will remain afterwards? A longer history needs capacity but can help when an erroneous change is discovered late. Requirements are agreed for the specific need; this article sets no blanket statutory retention period.
Measure restores regularly against a real task
A test restores a selected file or service in a suitable environment. A representative work task is then carried out. The actual time needed and missing dependencies are recorded and fed back into the plan.
DAXS combines PBS with Proxmox operations, separate backup paths, notifications and tested recovery. A useful starting point is a short list of particularly important applications with recovery objectives and responsible people. Suitable backup media or copies follow from the overall design; the cover image is not a complete backup recommendation.
Backup and recovery · Infrastructure and platforms · Plan recovery
Sources: Proxmox Backup: maintenance tasks (external link) · Proxmox Backup: client and pruning (external link)
