Simple, configuration-driven backup software for servers and workstations

Dan Helfman d372a86fe6 Code formatting. 3 years ago
.gitea 612e1fea67 Add database version to issue template. 5 years ago
borgmatic d372a86fe6 Code formatting. 3 years ago
docs 8336165f23 Update documentation with environment variable escaping (#546). 3 years ago
sample 3ecb92a8d2 Add randomized delay to systemd timer 3 years ago
scripts cb5fe02ebd Fix broken Bash completion end-to-end test. 3 years ago
tests d372a86fe6 Code formatting. 3 years ago
.dockerignore cd91dbd4f7 Include sub-command help in documentation. 6 years ago
.drone.yml 87001337b4 Merge master into mongodb_hook 3 years ago
.eleventy.js dcead12e86 Attempt to fix documentation build error introduced by Eleventy upgrade. 3 years ago
.gitignore cf8882f2bc Run arbitrary Borg commands with new "borgmatic borg" action (#425). 4 years ago
AUTHORS 6cdc92bd0c Fix for "borgmatic restore" showing success and incorrectly extracting archive files, even when no databases are configured to restore (#246). 5 years ago
LICENSE 7b3efddcbd Adding GPL v3 license. 10 years ago
MANIFEST.in 07222cd984 Fix visibility of "borgmatic prune --stats" output (#219). 5 years ago
NEWS cc32f0018b Start formalizing how new features are flagged by version in documentation. 3 years ago
README.md 0e90a80680 Add links in documentation for ntfy monitoring hook (#543). 3 years ago
SECURITY.md c63219936e Wording tweaks to security policy. 3 years ago
pyproject.toml 20b8b45aeb Remove all configuration from Tox file 6 years ago
setup.cfg c072678936 Add support for ruamel.yaml 0.17.x YAML parsing library (#404). 4 years ago
setup.py aecb6fcd74 Code style, rename command-line flag, and move new code into its own file (#546) 3 years ago
test_requirements.txt 48f44d2f3d Add tests for compact action (#394). 3 years ago
tox.ini 9317cbaaf0 Code formatting. 3 years ago

README.md


title: borgmatic

permalink: index.html

It's your data. Keep it that way.

borgmatic logo

borgmatic is simple, configuration-driven backup software for servers and workstations. Protect your files with client-side encryption. Backup your databases too. Monitor it all with integrated third-party services.

The canonical home of borgmatic is at https://torsion.org/borgmatic.

Here's an example configuration file:

location:
    # List of source directories to backup.
    source_directories:
        - /home
        - /etc

    # Paths of local or remote repositories to backup to.
    repositories:
        - 1234@usw-s001.rsync.net:backups.borg
        - k8pDxu32@k8pDxu32.repo.borgbase.com:repo
        - /var/lib/backups/local.borg

retention:
    # Retention policy for how many backups to keep.
    keep_daily: 7
    keep_weekly: 4
    keep_monthly: 6

consistency:
    # List of checks to run to validate your backups.
    checks:
        - name: repository
        - name: archives
          frequency: 2 weeks

hooks:
    # Custom preparation scripts to run.
    before_backup:
        - prepare-for-backup.sh

    # Databases to dump and include in backups.
    postgresql_databases:
        - name: users

    # Third-party services to notify you if backups aren't happening.
    healthchecks: https://hc-ping.com/be067061-cf96-4412-8eae-62b0c50d6a8c

Want to see borgmatic in action? Check out the screencast.

borgmatic is powered by Borg Backup.

Integrations

PostgreSQL      MySQL      MariaDB      MongoDB      Healthchecks      Cronitor      Cronhub      PagerDuty      ntfy      BorgBase     

Getting started

Your first step is to install and configure borgmatic.

For additional documentation, check out the links above for borgmatic how-to and reference guides.

Hosting providers

Need somewhere to store your encrypted off-site backups? The following hosting providers include specific support for Borg/borgmatic—and fund borgmatic development and hosting when you use these links to sign up. (These are referral links, but without any tracking scripts or cookies.)

  • BorgBase: Borg hosting service with support for monitoring, 2FA, and append-only repos

Additionally, rsync.net and Hetzner have compatible storage offerings, but do not currently fund borgmatic development or hosting.

Support and contributing

Issues

You've got issues? Or an idea for a feature enhancement? We've got an issue tracker. In order to create a new issue or comment on an issue, you'll need to login first. Note that you can login with an existing GitHub account if you prefer.

If you'd like to chat with borgmatic developers or users, head on over to the #borgmatic IRC channel on Libera Chat, either via web chat or a native IRC client. If you don't get a response right away, please hang around a while—or file a ticket instead.

Also see the security policy for any security issues.

Other questions or comments? Contact witten@torsion.org.

Contributing

borgmatic source code is available and is also mirrored on GitHub for convenience.

borgmatic is licensed under the GNU General Public License version 3 or any later version.

If you'd like to contribute to borgmatic development, please feel free to submit a Pull Request or open an issue first to discuss your idea. We also accept Pull Requests on GitHub, if that's more your thing. In general, contributions are very welcome. We don't bite!

Also, please check out the borgmatic development how-to for info on cloning source code, running tests, etc.

Build Status