SQLBackup turns a fragile pile of cron scripts into one dependable agent. Here's the whole flow — and you can play with it right on this page.
Tell SQLBackup how to reach each database. Run a one-click connection test. Keep passwords in environment variables, never in the config file.
A job ties a database to one or more destinations, a cron schedule, a backup type, and retention rules. Toggle compression and encryption per job.
Start SQLBackup and it runs continuously — firing each job on schedule, shipping offsite, pruning old copies, logging every result, and emailing you if anything fails.
Click each stage. Every backup streams through these four steps — nothing is ever fully loaded into memory.
Make a few choices and watch the config.yaml SQLBackup would use update in real time. No install required.
This is a real, valid SQLBackup config. Save it as config.yaml, set DB_PASSWORD in your environment, and run sqlbackup run.
A backup you can't restore is just wasted disk. With SQLBackup, recovery is one command — here's every step it runs.
No juggling openssl, gunzip, and psql by hand at the worst possible moment. SQLBackup handles the whole chain and restores into a database you name — so you can verify before promoting it.
Tip: practice restores on a schedule. An untested backup isn't a backup yet.
Install SQLBackup, add a job, and your databases are protected by tonight.
Start free trial Read the Docs