GoBackup

Use it when

• You run PostgreSQL, MySQL, Redis, or MongoDB on a self-managed server and need scheduled, compressed, encrypted dumps shipped to S3, GCS, or another cloud storage without hand-writing cron scripts.
• Your nightly backup cron jobs fail silently and you want Slack, webhook, or email notifications on backup success or failure plus storage-side recycling to control cost.

What it solves

Not the fit when

• Restore workflows are not documented in the README; independently define and regularly test restores.
• Not a replacement for replication, failover, managed snapshots, or point-in-time recovery.
• Database and storage credentials live in YAML configuration; restrict file permissions and avoid committing the file.
• database replication or failover
• point-in-time recovery
• automated restore orchestration
• application deployment

Install

Install with `brew install gobackup`, or review and run the project's installer from https://gobackup.github.io/install; the resulting binary is `gobackup`.

Invoke

Define models in ~/.gobackup/gobackup.yml (databases, storages, schedule), then run `gobackup perform` for a one-off backup or `gobackup start` to run the scheduling daemon with Web UI on port 2703.

Alternatives

No reviewed alternatives recorded yet.