mirror of
https://github.com/awesome-foss/awesome-sysadmin.git
synced 2026-05-11 15:50:26 -05:00
[PR #776] [CLOSED] Add Backup Manager to Backups section #5305
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/776
Author: @nomad4tech
Created: 4/24/2026
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
7155839Add Backup Manager to Backups section📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Add Backup Manager to Backups section
Thank you for taking the time to work on a PR for Awesome-Sysadmin!
Your additions are Free software
Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors
Submit one item per pull request.
Format your submission as follows...
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement
You have searched the repository for any relevant issues or PRs
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative
Why is it awesome?
Backup Manager is a self-hosted web UI for scheduling PostgreSQL, MySQL and MariaDB
backups from Docker containers. Dumps run inside the container via Docker exec API,
so pg_dump always matches the database version and no credentials need to be stored
in config files. Supports S3 upload, email notifications, heartbeat monitoring,
and automatic file rotation.
Have you used it? For how long?
Yes, I am the author and have been running it on my own production servers
since the initial release.
Is this in a personal or professional setup?
Personal/homelab setup, managing databases across multiple servers.
How many devices/users/services/... do you manage with it?
Multiple remote Docker hosts with several databases, tested on databases up to 500 GB.
Biggest pros/cons compared to other solutions?
Pro: No credentials stored in config files, dump tool always matches DB version,
simple single docker-compose setup, web UI with no CLI required.
Con: Linux only, early stage project, single maintainer.
Any other comments?
The project is actively maintained and open to contributions.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.