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, we've got a plan in place to repurpose the old fileserver as a new archive server. Needs the purchase of two largish NAS hard drives, and a full refresh of the OS and some scripting etc, but after that, we're good to go.
I'm gonna put #guix on it so it's reproducible in case the old device dies (motherboard is 9 years old), and gonna use #borgmatic to do the internal and offsite backup drives. The deduplication should make all this stuff work and we should be able to keep years of history
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:
borgmatic
Daniel Lakeland
Björns Techblogalias: 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.
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
I wrote about how I backup Incus instances or storage pool volumes with Borgmatic: https://maveonair.dev/backup-incus-with-borgmatic/
At the time of writing, Incus itself does not offer a backup scheduling feature. However, the Incus CLI has an export command for instances and storage pool volumes that can be used to create a gzip archive for an instance or storage pool volume. Since I use Borgmatic for backups, we can configure it so that certain instances or storage pool volumes are exported to a specific location before the backup and are cleaned up after the backup.
Given that the NixOS module for borgbackup mostly implements the things borgmatic would cover, what would be the advantage in using the borgmatic NixOS module instead?
BjoernAusGE
Fabian Mettler
chaos enby (libvirt/networking rabbithole arc)