Workspace for adding Uptime Kuma hook to official borgmatic
Find a file
2019-11-02 16:38:50 -07:00
.gitea In issue template, use python3 instead of python. 2019-08-24 13:08:18 -07:00
borgmatic Handle log file error more consistently with other error. Add --log-file-verbosity flag. Add docs. 2019-11-02 11:23:18 -07:00
docs Fix logging docs typo. 2019-11-02 12:54:03 -07:00
sample Merge sample cron files. 2019-09-24 10:49:46 -07:00
scripts Attempt to upgrade version of pip used in CI. 2019-10-31 20:37:01 -07:00
static Adding missing PNG logo. 2017-10-28 10:31:30 -07:00
tests Handle log file error more consistently with other error. Add --log-file-verbosity flag. Add docs. 2019-11-02 11:23:18 -07:00
.dockerignore Include sub-command help in documentation. 2019-06-22 22:04:56 -07:00
.drone.yml Add Python 3.8 to build matrix. 2019-11-02 16:38:50 -07:00
.eleventy.js Database dump hooks documentation (#225). 2019-10-23 15:35:37 -07:00
.gitignore Config generation support for sequences of maps, needed for database dump hooks (#225). 2019-10-21 15:17:47 -07:00
AUTHORS Add validate-borgmatic-config command 2019-05-10 00:10:28 +02:00
LICENSE Adding GPL v3 license. 2014-11-18 18:22:51 -08:00
MANIFEST.in Fix visibility of "borgmatic prune --stats" output (#219). 2019-09-23 13:07:51 -07:00
NEWS Add missing PR link. 2019-11-02 11:27:05 -07:00
pyproject.toml Remove all configuration from Tox file 2019-05-14 13:17:15 +02:00
README.md Documentation for database restores (#229). 2019-10-31 21:45:47 -07:00
setup.cfg Suppress part of an obnoxious warning about disabling coverage (for end-to-end tests). 2019-06-13 14:15:08 -07:00
setup.py Handle log file error more consistently with other error. Add --log-file-verbosity flag. Add docs. 2019-11-02 11:23:18 -07:00
test_requirements.txt Update test requirements. 2019-11-01 12:18:35 -07:00
tox.ini Attempt to upgrade version of pip used in CI. 2019-10-31 20:37:01 -07:00

title permalink
borgmatic index.html

Build Status

Overview

borgmatic logo

borgmatic is simple, configuration-driven backup software for servers and workstations. Backup all of your machines from the command-line or scheduled jobs. No GUI required. Built atop Borg Backup, borgmatic initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. borgmatic supports specifying your settings in a declarative configuration file, rather than having to put them all on the command-line, and handles common errors.

Here's an example config file:

location:
    # List of source directories to backup. Globs are expanded.
    source_directories:
        - /home
        - /etc
        - /var/log/syslog*

    # Paths to local or remote repositories.
    repositories:
        - user@backupserver:sourcehostname.borg

    # Any paths matching these patterns are excluded from backups.
    exclude_patterns:
        - /home/*/.cache

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

consistency:
    # List of consistency checks to run: "repository", "archives", etc.
    checks:
        - repository
        - archives

hooks:
    # Preparation scripts to run, databases to dump, and monitoring to perform.
    before_backup:
        - prepare-for-backup.sh
    postgresql_databases:
        - name: users
    healthchecks: https://hc-ping.com/be067061-cf96-4412-8eae-62b0c50d6a8c

borgmatic is hosted at https://torsion.org/borgmatic with source code available. It's also mirrored on GitHub for convenience.

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

How-to guides

Reference guides

Hosting providers

Need somewhere to store your encrypted offsite backups? The following hosting providers include specific support for Borg/borgmatic. Using these links and services helps support borgmatic development and hosting. (These are referral links, but without any tracking scripts or cookies.)

  • rsync.net: Cloud Storage provider with full support for borg and any other SSH/SFTP tool
  • BorgBase: Borg hosting service with support for monitoring, 2FA, and append-only repos

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 Freenode, either via web chat or a native IRC client.

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

Contributing

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.