Search
57 results for “borgmatic”
-
borgmatic 2.1.5 has been released with mTLS support for the Loki monitoring hook and several fixes.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.5
-
borgmatic 2.1.4 has been released with a stand-alone Linux binary, "info" and "repo-list" performance improvements, and several fixes.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.4
-
borgmatic 2.1.3 has been released with a "diff" action to show deltas between archives, a "config show" action to get computed borgmatic configuration, "spot" check improvements, and more.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.3
-
Ok, thanks to @borgmatic I have a backup that is running and sending data to a repurposed backup drive that used to be formatted to my old backup scheme and is now fully assimilated to the borg.
I'm gonna run it for a few weeks, then convert my other hard drive that I swap between... and once those have run for a month or two I'll swap one of them to my offsite location and convert my current offsite drive. Slow, steady, and with a fallback at all times!
-
#borgmatic friends. I have several backup drives that I rotate through. If I list each of their mount points in the borgmatic config, and the drive isn't mounted so the path doesn't exist, will borgmatic error out, or continue with the additionally listed destinations?
ideally It'd just update whatever drives I have mounted, and skip over whatever ones I don't.
-
borgmatic 2.1.2 has been released with fixes to unicode decoding, consistency checks, and the ntfy monitoring hook.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.2
-
Borgmatic notifications via Home Assistant
https://blog.sengotta.net/borgmatic-notifications-via-home-assistant/In the past i normally used Telegram for all kinds of notifications in my smarthome and homelab. I mean it simply was easy and convenient with its bot feature. But the platform become more and more ethical problematic in the past years. Thats quite sad because back in 2013 it was a really good alternative to Whatsapp (which i never used). Crossplattform with optional encryption and not owned by some Techbros from Silicon Valley. Nevertheless: nowadays you connect Telegram with Terrorism, Fascists and all kind of bogus people who run their extremist platforms on the Telegram Channel feature. You now could say: dont kill the messenger, but i better chose to migrate.
Migrating my Borgmatic notifications is not hard at all but there is a small caveat because Borgmatic uses yaml files use colons as delimiter, which is kind of bad when you use curl to pass a json payload.
But first of all you need a Webhook endpoint in Home Assistant for your notification. This is really easy done. Navigate to Atutomations & Scenes in HA than add a new automation and paste the following yaml:
alias: Borgmatic backup notification description: Sends backup notifictaions triggers: - webhook_id: backup_notification allowed_methods: - POST local_only: false trigger: webhook conditions: [] actions: - data: message: "{{ trigger.json.Message }}" title: Backup Status action: notify.your_smartphone_etc mode: singleRemember this is a yaml, so no tabs but spaces for indentation. Obviously you can change alias, description, webhook_id and put your smartphone etc into the action. Thats it for the Home Assistant part.
Next you need to put the correct commands into the Borgmatic config.yaml so that the currect curl command will be triggered when a backup ist started, finished or failed. I will just post the hook section here which is needed.
hooks: before_backup: - echo "Starting a backup." - > /usr/bin/curl -X POST -H "Content-Type: application/json" -d '{"Message":"Started Backup"}' http://YourHAIP:8123/api/webhook/backup_notification after_backup: - echo "Finished a backup." - > /usr/bin/curl -X POST -H "Content-Type: application/json" -d '{"Message":"Finisched Backup"}' http://YourHAIP:8123/api/webhook/backup_notification on_error: - echo "Error during prune/create/check." - > /usr/bin/curl -X POST -H "Content-Type: application/json" -d '{"Message":"Backup Error"}' http://YourHAIP:8123/api/webhook/backup_notificationSorry for the bad formatting in WordPress. The special thing is that you need to use multiline yaml (recognizeable because of the – > ), i tried puttung the whole curl commands in braces which did not work.
#borgmatic #homeassistant #selfhosting #telegram @bjoern
Nevertheless, i get me notifications now onto my smartphone via Home Assistant. Dont know if that is the end of the journey or if i will switch one time to Matrix or XMPP for my notifications.
By the way this may not only work with Home Assistant but also with all other services receiving their data via Webhooks and json payload.
Have fun -
borgmatic 2.1.1 has been released with fixes to the "spot" check, the KeePassXC credential hook, and the ntfy monitoring hook.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.1
-
borgmatic 2.1.0 has been released with many logging, memory, and performance improvements.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.1.0
-
love this explicit statement on #borgmatic manual https://torsion.org/borgmatic/reference/configuration/repositories/#s3-%2F-b2
"When selecting your cloud hosting provider, be aware that Amazon in particular has financially supported the Trump regime." #fcktrmp -
borgmatic 2.0.13 has been released with file/archive list format configuration, MariaDB/MySQL Unix socket path support, Btrfs performance improvements, and more.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.13
-
borgmatic 2.0.12 has been released with an "ask_for_password" option for the KeePassXC credential hook, plus fixes for Btrfs, fish shell completions, and database hooks.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.12
-
margau.net has now (finally!) some updated (#borgmatic 2.x) documentation on how to monitor backups with #prometheus: https://margau.net/posts/2024-08-02-borgmatic-prometheus/
Remember: The backup only exists if you have verified its existence!
-
borgmatic 2.0.11 has been released with fixes, fixes, and more fixes. Also environment support in the Sentry monitoring hook.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.11
-
borgmatic 2.0.10 has been released with "borg_extra_options" for all Borg commands, MariaDB/MySQL database dump skipping, runtime directory fixes, reference documentation, and more.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.10
-
borgmatic 2.0.9 has been released with ZFS, Btrfs, and LVM improvements, more flexible systemd credentials, and support for Python 3.14.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.9
-
Uh, whats up with #borgmatic and its domain, torsion.org? Seems like both its nameservers are down.
-
borgmatic 2.0.8 has been released with database container support, database labels, and fixes for LVM, the "spot" check, and Borg 2.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.8
-
borgmatic 2.0.7 has been released with Btrfs improvements, Borg 2 features, and security fixes.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.7
-
borgmatic 2.0.6 has been released with fixes for the "spot" check, the "config generate" action, and the LVM hook.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.6
-
Summer vacations are all about having a good time, and finding time to work on your opensource project. 🌴
Some great features are coming to BorgWarehouse in the next few days, including API repository control!
Stay tuned, v2.4.0 is coming 💫
-
Another task completed for the home lab. Something that should have been done earlier. :yikes:
Got BorgMatic backups running on my workhorse server that hosts postmarks, gotosocial, owncast and a few websites. They are being pushed to the cloud (BorgBase) and to an attached storage drive.
Backing up daily, weekly, and monthly via cron job.
Verified backups can be restored. 🎉
-
Spent some time learning about BorgMatic, Borg Backup, and BorgBase. I'm borged out. Made some progress, not as much as I'd hoped.
Running this instance in a container and then changing some of the default volume locations was a mistake. Lesson learned.
-
@cryptgoat Unless you want to be writing your own backup scripts, you should probably compare the higher-level backup software that wraps each of #Restic and #BorgBackup. For instance: #autorestic and #borgmatic.
-
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
Finally moved the Borgmatic Notifications from Telegram to Homeassistant so i can now abbandon Telegram.
#selfhosting #telegram #homeassistant #borgmatic @homelab