|Dan Helfman 94b9ef56be Change "exclude_if_present" option to support multiple filenames, rather than just a single filename (#280).||2 hours ago|
|.gitea||2 months ago|
|borgmatic||2 hours ago|
|docs||1 day ago|
|sample||2 days ago|
|scripts||1 month ago|
|tests||2 hours ago|
|.dockerignore||7 months ago|
|.drone.yml||1 month ago|
|.eleventy.js||2 months ago|
|.gitignore||3 months ago|
|AUTHORS||2 months ago|
|LICENSE||5 years ago|
|MANIFEST.in||4 months ago|
|NEWS||2 hours ago|
|README.md||4 days ago|
|pyproject.toml||8 months ago|
|setup.cfg||7 months ago|
|setup.py||1 day ago|
|test_requirements.txt||2 months ago|
|tox.ini||1 month ago|
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.
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: - email@example.com:backups.borg - k8pDxu32@k8pDxu32.repo.borgbase.com:repo - /var/lib/backups/backups.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: - repository - archives 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.
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.