Your PostgreSQL Backups Are Probably Broken (Here's How to Know for Sure)

Kjudeh — Thu, 19 Feb 2026 05:17:25 +0000

73% of backup restores fail in production.

Not because the backup software broke. Because no one tested the restore.

I've been running PostgreSQL in production for years. I've seen teams religiously back up their databases every hour, upload to S3, check the green checkmark, and sleep soundly. Then disaster hits, they try to restore, and... nothing works. Corrupted dumps. Wrong permissions. Missing extensions. Schema drift.

The backup worked. The restore didn't. And they only found out when it mattered most.

The Problem With "Just Back It Up"

Most backup setups look like this:

pg_dump → gzip → S3 →✓ done

That checkmark is a lie. It tells you the file uploaded. It doesn't tell you:

Can this dump actually be restored?
Will the data be intact?
Do the row counts match?
Are the indexes valid?

You don't know until you try. And most teams never try until it's too late.

The Fix: Automated Restore Verification

I built a backup system that doesn't just dump and pray. Every day, it:

Downloads the latest backup from S3
Restores it to an isolated verification database
Runs integrity checks (table counts, row validation, custom queries)
Reports success or failure
Cleans up automatically

If the restore fails, I know immediately — not when production is on fire.

How It Works

The system has two services:

Backup Service — Runs pg_dump on a schedule (default: hourly), compresses with gzip, uploads to any S3-compatible storage. Handles retention automatically.

Verify Service — Downloads backups daily and restores them to a separate PostgreSQL instance. Runs sanity checks. Proves the backup works.

Both run as lightweight containers. Works with AWS S3, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, Wasabi, or MinIO.

One-Click Deploy on Railway

If you're running PostgreSQL on Railway, you can deploy this in minutes:

Just add your database URL and S3 credentials. The services start working immediately.

What you get:

Hourly backups to S3 (configurable)
Daily restore verification
7-day retention (configurable)
AES-256 encryption (optional)
Slack/Discord alerts on failure
Zero maintenance after setup

The Code

Fully open source:

GitHub: github.com/Kjudeh/railway-postgres-backups

Works with Docker, docker-compose, or any container platform — not just Railway.

Stop Hoping. Start Verifying.

Every backup you haven't restored is a backup you can't trust.

Set up automated verification once. Sleep better forever.

Questions? Drop a comment or open an issue on GitHub.