01 / THE ROLE
In this lab.
Proxmox Backup Server provides a backup datastore for the virtualised estate, with NAS-backed storage documented for the datastore. It is a distinct component from the Proxmox hosts that run the VMs. A configured job or reachable datastore is not presented here as proof of complete recoverability.
02 / THE CONNECTIONS
Follow the flow.
- STEP 01Virtual machine backup
- STEP 02PBS datastore
- STEP 03Retained backup
- STEP 04Isolated restore
03 / How it works
How it works.
The backup workflow captures the VM-level recovery object. To judge its value, check which VM is included, whether a recent job completed, what data the backup contains and whether a restore can perform a meaningful application operation. Newly promoted services need explicit backup and recovery follow-up.
04 / Persistent data & recovery
Persistent data & recovery.
Recovery includes access to the datastore and any required keys, configuration and credentials, not only the guest backup. For services with databases or external mounts, establish which state is inside the VM and which state must be recovered separately.
05 / How to check it
How to check it.
Check job results, backup age, expected inclusion, datastore availability and restore evidence. A successful login to PBS proves only one layer. A restored guest booting is the start of validation, not the end.
06 / Decisions & limits
Decisions & limits.
VM backups are a useful recovery layer, but application consistency and shared-storage dependencies still matter. The roadmap includes regular restore testing across files, databases, applications, VMs and supporting infrastructure; the full programme is not yet a completed claim.