SQLBackup is one tool for your whole database stack: dump with native tools, compress, encrypt, ship offsite on a schedule, monitor, and restore. All free and open-source.
SQLBackup uses each database's own official tools, so your dumps are exactly what the vendor intends.
PostgreSQL, MySQL, MariaDB, SQL Server (incl. Azure SQL & RDS) and MongoDB — one consistent workflow for all of them.
AES-256-GCM with a scrypt-derived key, applied before upload. Each chunk is independently authenticated.
Backups are gzip-compressed on the fly — often 70–80% smaller — without ever loading the whole dump into memory.
Send each backup to several places at once, each with its own retention policy.
A continuous scheduler runs every job on a standard 5-field cron expression and keeps going as an agent.
Keep the last N copies or N days of history — configured independently for every destination.
Every run is logged to a local SQLite database, surfaced as health %, sizes and a "needs attention" list.
Get an email the moment a backup fails (and optionally on success) over standard SMTP/TLS.
Download, decrypt, decompress and restore from any destination in a single step — into a fresh database if you like.
Mix and match. The same encrypted backup can land in several places for real redundancy.
A folder on disk or a mounted network share — the fastest, simplest target.
Durable object storage with lifecycle rules. The classic offsite destination.
Wasabi, Backblaze B2, MinIO and others via a custom endpoint URL.
Any SSH/SFTP server — your own box, a partner's, or managed file storage.
Every job writes a timestamped, color-coded log line. Watch a backup flow from dump to upload — and see exactly how failures are surfaced and retried.
A native window with a friendly dashboard — Overview, Jobs, Restore, Monitoring, Alerts.
init · test · backup · restore · history · status · run — scriptable everywhere.
Verify database and destination connectivity before you trust a schedule.
Reference passwords by environment variable name — keep secrets out of config files.
Runs as a desktop app or a headless agent on either platform.
Run an agent per server and see them all reporting in from one dashboard.
GCM authentication means a corrupted or altered backup fails to decrypt — loudly.
MIT licensed. Read the code, audit the crypto, contribute, or fork it.
AES-256-GCM, key via scrypt (n=2¹⁴), per-file salt, per-chunk nonce