|Dan Helfman dbf8301c19||3 months ago|
|.gitea||4 years ago|
|borgmatic||3 months ago|
|docs||3 months ago|
|sample||8 months ago|
|scripts||8 months ago|
|tests||3 months ago|
|.dockerignore||4 years ago|
|.drone.yml||10 months ago|
|.eleventy.js||9 months ago|
|.gitignore||2 years ago|
|AUTHORS||4 years ago|
|LICENSE||9 years ago|
|MANIFEST.in||4 years ago|
|NEWS||3 months ago|
|README.md||5 months ago|
|SECURITY.md||2 years ago|
|pyproject.toml||4 years ago|
|setup.cfg||2 years ago|
|setup.py||3 months ago|
|test_requirements.txt||6 months ago|
|tox.ini||1 year ago|
It's your data. Keep it that way.
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: - ssh://email@example.com/./backups.borg - ssh://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.
Your first step is to install and configure borgmatic.
For additional documentation, check out the links above for borgmatic how-to and reference guides.
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
Are you experiencing an issue with borgmatic? Or do you have an idea for a feature enhancement? Head on over to our issue tracker. In order to create a new issue or add a comment, you'll need to register first. If you prefer to use an existing GitHub account, you can skip account creation and login directly.
Also see the security policy for any security issues.
Check out the Borg subreddit for general Borg and borgmatic discussion and support.
Also follow borgmatic on Mastodon.
To chat with borgmatic developers or users, check out the
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.
Other questions or comments? Contact firstname.lastname@example.org.
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 to discuss your idea. Note that you'll need to register first. 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.