this post was submitted on 09 Jul 2026
6 points (100.0% liked)

DevOps

2188 readers
15 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 3 years ago
MODERATORS
 

Honest question. I've got automated daily pg_dump backups going to S3 and I check that the files are there, but I've never actually tried restoring one on a fresh instance to see if it works.

Feel like this is one of those things where you assume it's fine until you desperately need it and find out the dumps were corrupted for 3 months.

Anyone have a setup where restores get tested automatically? Or is that overkill for side projects?

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 1 points 11 hours ago

I noticed I could not restore pg dumps as expected when migrating to a new server. I had to add some parameter to pg dump so it's a better/more neutral dump or something, which was easier/able to restore. So - definitely check your backups.

Trying the restore locally is also an option. Just to verify it works and the expected data is there.

How important it is to verify and verify regularly depends on how much loss you're willing to accept.

Once verified, as long as you don't do big version upgrades or automation changes, I would expect it to continue to work indefinitely. A semi regular verification still makes sense, though.

At work I know my DB backups definitely work for other reasons, due to regular restores in non-prod.

For side projects I definitely recommend verifying it at least once, when setting up automated backups/scripts for backup creation.