|Dan Helfman c12c47cace Fix "borgmatic list --successful" with a slightly better heuristic for listing successful (non-checkpoint) archives.||3 months ago|
|.gitea||4 months ago|
|borgmatic||3 months ago|
|docs||3 months ago|
|sample||3 months ago|
|scripts||3 months ago|
|static||2 years ago|
|tests||3 months ago|
|.dockerignore||6 months ago|
|.drone.yml||3 months ago|
|.eleventy.js||3 months ago|
|.gitignore||7 months ago|
|AUTHORS||8 months ago|
|LICENSE||5 years ago|
|MANIFEST.in||3 months ago|
|NEWS||3 months ago|
|README.md||3 months ago|
|pyproject.toml||8 months ago|
|setup.cfg||7 months ago|
|setup.py||3 months ago|
|test_requirements.txt||3 months ago|
|tox.ini||7 months ago|
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", or both. checks: - repository - archives
Want to see borgmatic in action? Check out the screencast.
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.)
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 firstname.lastname@example.org.
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.