Workspace for adding Uptime Kuma hook to official borgmatic
Find a file
2019-02-03 22:42:33 -08:00
borgmatic Leave exclude_patterns glob expansion to Borg, since doing it in borgmatic leads to confusing behavior (#132). 2019-01-27 13:47:26 -08:00
docs/how-to Include link to development how-to. 2019-02-03 22:42:33 -08:00
sample Add example for cron in Alpine Linux (#24) 2018-09-05 21:58:30 -07:00
scripts Support for Borg create & prune --stats via borgmatic command-line flag (#100) 2018-12-22 23:27:24 +01:00
static Adding missing PNG logo. 2017-10-28 10:31:30 -07:00
tests Leave exclude_patterns glob expansion to Borg, since doing it in borgmatic leads to confusing behavior (#132). 2019-01-27 13:47:26 -08:00
.drone.yml Add Python 3.5 to continuous integration. 2018-10-15 08:17:34 -07:00
.gitignore Upgrade ruamel.yaml compatibility version range and fix support for Python 3.7 (#38, #76). 2018-07-22 11:25:06 -07:00
AUTHORS Rework logging/verbosity system (#90) 2018-09-08 20:53:37 +00:00
LICENSE Adding GPL v3 license. 2014-11-18 18:22:51 -08:00
MANIFEST.in Basic YAML configuration file parsing. 2017-07-04 16:52:24 -07:00
NEWS Refactor documentation into multiple separate pages for clarity and findability. 2019-02-03 22:20:59 -08:00
README.md Refactor documentation into multiple separate pages for clarity and findability. 2019-02-03 22:20:59 -08:00
setup.cfg No longer producing univeral (Python 2 + 3) wheel. 2017-07-23 17:34:17 -07:00
setup.py Refactor documentation into multiple separate pages for clarity and findability. 2019-02-03 22:20:59 -08:00
test_requirements.txt Make automated tests support running in Python 3.5. 2018-10-15 09:04:29 -07:00
tox.ini Switch from bash to sh for black wrapper. 2018-10-15 09:25:57 -07:00

title permalink
borgmatic borgmatic/index.html

Overview

borgmatic is a simple Python wrapper script for the Borg backup software that initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. The script 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", or both.
    checks:
        - repository
        - archives

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

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.

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.

Troubleshooting

Broken pipe with remote repository

When running borgmatic on a large remote repository, you may receive errors like the following, particularly while "borg check" is validating backups for consistency:

    Write failed: Broken pipe
    borg: Error: Connection closed by remote host

This error can be caused by an ssh timeout, which you can rectify by adding the following to the ~/.ssh/config file on the client:

    Host *
        ServerAliveInterval 120

This should make the client keep the connection alive while validating backups.

libyaml compilation errors

borgmatic depends on a Python YAML library (ruamel.yaml) that will optionally use a C YAML library (libyaml) if present. But if it's not installed, then when installing or upgrading borgmatic, you may see errors about compiling the YAML library. If so, not to worry. borgmatic should install and function correctly even without the C YAML library. And borgmatic won't be any faster with the C library present, so you don't need to go out of your way to install it.