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.
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.
Already live in the product
Running in production today: real database backup jobs and a scheduled verification drill that checks every dump is complete.
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
What teams can do here
- Step 1Set a backup policy
- Step 2Backups run on schedule
- Step 3Weekly drill validates the latest backup
- Step 4Review drill evidence
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.
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.
Frequently asked questions
See also: Server monitoring · Server provisioning (InfroStack) · Blog: Server monitoring tools · Blog: RMM tools compared · Reports & automation
Book demo
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.
