Simple, configuration-driven backup software for servers and workstations
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Dan Helfman 76c569cf84 Update test requirements. 1 year ago
.gitea In issue template, use python3 instead of python. 1 year ago
borgmatic Monitor backups with Cronitor hook integration. 1 year ago
docs Monitor backups with Cronitor hook integration. 1 year ago
sample Merge sample cron files. 1 year ago
scripts Attempt to upgrade version of pip used in CI. 1 year ago
static Adding missing PNG logo. 3 years ago
tests Monitor backups with Cronitor hook integration. 1 year ago
.dockerignore Include sub-command help in documentation. 1 year ago
.drone.yml Upgrade build to Alpine 3.10. 1 year ago
.eleventy.js Database dump hooks documentation (#225). 1 year ago
.gitignore Config generation support for sequences of maps, needed for database dump hooks (#225). 1 year ago
AUTHORS Add validate-borgmatic-config command 1 year ago
LICENSE Adding GPL v3 license. 6 years ago Fix visibility of "borgmatic prune --stats" output (#219). 1 year ago
NEWS Monitor backups with Cronitor hook integration. 1 year ago Documentation for database restores (#229). 1 year ago
pyproject.toml Remove all configuration from Tox file 1 year ago
setup.cfg Suppress part of an obnoxious warning about disabling coverage (for end-to-end tests). 1 year ago Monitor backups with Cronitor hook integration. 1 year ago
test_requirements.txt Update test requirements. 1 year ago
tox.ini Attempt to upgrade version of pip used in CI. 1 year ago

title permalink
borgmatic index.html

Build Status


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:

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

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

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

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

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

    # Preparation scripts to run, databases to dump, and monitoring to perform.
        - name: users

borgmatic is hosted at 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.)

  • 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


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


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.