Clear guidance for operators protecting Linux servers, Docker stacks, databases, and restic repositories—without pretending a green check is the same as a tested restore.
All guides
Page 3 of 5 · 40 guides
A clean repository check is important evidence about stored backup data. It is not evidence that you selected the right sources or can recover the application.
A Compose file can recreate containers, but it cannot recreate the state around them. Map every persistent dependency, protect it correctly, and rehearse the order of recovery.
Hetzner Backups, Snapshots, and independent backups solve different recovery problems. Use this comparison to decide which layers your server actually needs.
A VPS snapshot captures disk state. A database backup captures a recoverable database state, with consistency, scope, logs, and restore behavior the engine understands.
Both create encrypted, deduplicated snapshots. The decisive differences appear in policy management, built-in interfaces, and how a team shares repository access.
A backup monitor must catch command failures and jobs that never started. Here is how to cover both without turning every warning into a page.
pg_dump protects one database; pg_dumpall covers the cluster and global objects. The restore path is different enough to decide up front.
A single-database mongodump can overlap live writes and still lack one point-in-time boundary. This workflow makes that limitation explicit and tests the archive safely.
The same restic repository works across several object stores. The meaningful differences are credentials, endpoints, access controls, and who operates the storage.