Blog
Long-form on backup independence for Postgres — restore evidence, audit chains, and recoverability you can prove.
- self-hosting postgres backups after pgBackRest — separate the workflows first
physical backup tooling and Walwarden's logical-backup workflow solve different operational problems.
- neon recovery and logical backups — two distinct workflows
a provider recovery feature and a configured logical-backup destination should be evaluated as separate workflows.
- supabase recovery and off-service logical backups — a decision guide
compare a provider recovery feature with a configured customer-owned S3 backup workflow without treating them as interchangeable.
- what pg_dump records — and what needs separate evidence
a logical dump records database contents at a point in time; restore outcome, integrity, and workflow history require separate artifacts.
- backup independence — define the destination and restore operator
make backup destination, access, billing, and restore operation explicit instead of relying on an ownership slogan.
- why walwarden exists
a backup file, restore outcome, integrity record, and workflow history are distinct artifacts.