Database Backup and Restore with Veeam Kasten
Solution overview
This lab implements an end-to-end data protection solution for a stateful,
containerized application. The Customer CRM keeps its records in a
PostgreSQL database, and the objective is to recover that data quickly and
consistently after loss or corruption. Three components work together to
make that possible:
- Veeam Kasten orchestrates protection through policies — it decides
what to protect, when, and where backups are stored, and it drives
both backup and restore operations. - A Kanister Blueprint defines how to capture the database in an
application-consistent way. Rather than copying raw disk blocks, it
runspg_dumpso the backup is a clean, transactionally consistent copy
of the data. - A Location Profile is the external destination — NFS file storage in
this lab — where backups are exported and kept safe outside the cluster.
Because the NFS storage here has no CSI volume snapshots, Veeam Kasten uses
the blueprint to move the database contents during the backup itself. A
backup therefore flows like this: Veeam Kasten runs the policy → the
blueprint executes pg_dump against the live database → the dump is
exported to the Location Profile. A restore reverses that flow: Veeam
Kasten pulls the backup from the Location Profile → the blueprint replays it
into the database → the application is returned to its protected state.
By the end of the lab you will have run this full cycle: protect the CRM,
simulate data loss, and restore all 500 customer records from the exported
backup.