New · Release 2026.04, Multi-tenant audit exports & SLA dashboards now liveSee changelog →
Business continuity
Backups and disaster recovery you can actually prove
Scheduled encrypted PostgreSQL backups with retention and pruning, plus a weekly automated drill that re-checks the latest backup, validates it as a complete dump and logs its age.
Product illustration · sample data
Infrastructure / Live
142/142 healthy
CPU avg
34%
Memory avg
62%
api-prod-01.acme.io98ms
db-primary.acme.io12ms
worker-eu-03.acme.ioSSL expires 14d
Product proof
Already live in the product
Backed by app modules
Running in production today: real database backup jobs and a scheduled verification drill that checks every dump is complete.
Protected app route: /backups
How it works
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
Scheduled encrypted database backups
Retention and automatic pruning
Weekly automated verification drill
Backup age and drill result logged
Workflow
What teams can do here
Step 1
Set a backup policy
Step 2
Backups run on schedule
Step 3
Weekly drill validates the latest backup
Step 4
Review drill evidence
How it works
How it works
01
Set a backup policy
A platform-wide policy controls whether backups run and how many are kept — a retention count (14 by default) plus an age cap in days (30 by default) after which older successful backups are pruned.
02
Run backups on schedule
A scheduled job takes a real pg_dump of the database, records its size and a SHA-256 checksum, and stores it. If no policy exists at all it still runs with safe defaults rather than silently doing nothing.
03
Verify backups weekly
A weekly drill re-checks the latest backup's SHA-256, decrypts and decompresses it in memory, and validates it as a complete pg_dump with its table and row counts. No database is created or restored, and it never touches the live database.
04
Review drill evidence
Each drill logs its result, the tables and rows it found and the backup's age (how old the checked backup was), so backup health is measured, not assumed.
Example
A worked example
Say a diagnostics-lab chain is going through an ISO-style audit and the assessor asks the classic question: "when did you last check that a backup is usable?" The retention policy keeps the last 14 dumps and prunes anything past 30 days. Every week the drill re-checks the newest dump's checksum, validates it as a complete dump and confirms its table count sits within range of the live schema, without restoring anything. The lab's answer is a drill history: a pass with a backup under a day old, week after week — evidence on a screen instead of an assurance in a meeting.
FAQ
Frequently asked questions
What exactly gets backed up?
The platform PostgreSQL database — the data behind your workspace — via real pg_dump jobs. Backups are a platform-wide operation, and each job records its file size and a SHA-256 checksum.
How do you know a backup can actually be restored?
A scheduled drill re-checks the latest backup's SHA-256, decrypts and decompresses it in memory, and only passes when it is a complete pg_dump (every data block closed, the completion trailer present) with a table count of at least about 90% of the live schema — catching a cut-short dump that a naive check would wave through. It validates the backup; it does not restore it into a database.
What do RTO and RPO mean here?
RTO is recovery time and RPO is how old the recoverable data is. The drill validates the backup without restoring it, so RTO is not measured; the backup's age (the RPO side) is logged on every drill, so you can show how recent the backed-up data is.
How is retention controlled?
The policy keeps a fixed number of recent backups (14 by default) and also drops successful backups older than a set number of days (30 by default). Pruning runs as its own task so old dumps do not pile up.
Does the backup drill risk my live data?
No. The drill only reads the backup file and validates it in memory. It creates no database and writes nothing to the live one, so verification cannot disturb production.
What happens when a drill fails?
The drill run is recorded with its outcome, so a backup that is incomplete or corrupted shows up in the drill history the week it happens — while there is time to fix the backup chain — rather than being discovered during an actual disaster.
What can I hand to an auditor from this module?
The backup history with sizes and SHA-256 checksums, the retention policy in force, and the weekly drill log with the result and backup age per run — a verification record built from executed checks, not a written procedure.
Is your latest backup actually complete? Check it weekly
Checksummed pg_dump backups on a retention policy, plus an automated weekly drill that validates every dump is complete — backup health as a logged fact, not an untested assumption.