#DigitalIndependenceDay meets #WorldBackupDay (March 31st)! Backups are key to #digital #sovereignty. My 3-2-1 strategy: 3 copies, 2 media, 1 offsite — no #hyperscaler needed. I recently migrated from #BorgBackup to #Restic: better multi-repo flexibility, same solid encryption and deduplication. Offsite storage goes to a #Hetzner Storage Box, which is significantly cheaper than #AWS #S3 and the data remains in #Europe.

https://di.day

#did #diday #didit #ididit #dut #dutgemacht

Major improvements to #Borgbackup coming soon!

https://github.com/borgbackup/borg/discussions/9555

@felimwhiteley

Getting Borg backups to work on Nextcloud without an intermediary step was way more painful than it should have been and largely came down either a missing step in the documentation or a bug. I'll file a bug later and report back but in the meantime if you're new to #nextcloud and pulling your hair out because your remote #borgbackup won't work, the fix is fairly simple. Once you create the remote borg repo you need to copy the config file from the borg repository to the data directory of your nextcloud-aio container. So the steps look like this:

export BORG_REPO=ssh://[email protected]/path/to/repo

export BORG_PASSPHRASE=whatever you like

borg init -e repokey-blake2

cp /path/to/repo/config /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/borg.config

chown www-data:www-data /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/borg.config

chmod 0770 /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/borg.config

So following above, you're creating your repo on host zzz.zzz.zzz.zzz (replace this with the IP address of the target) and then once that's done you're copying the config file that gets created in the borg repo into the data directory for the Nextcloud Master Container. It looks like this maybe worked on older versions so my guess is this is a bug but anyway, there you go, this should fix the issue with your backups not working. They'll hopefully fix this at a later date.

I am considering #backup these days.

How to implement?
something about retention time, deduplication, ssh access, different clients not having access to each others data, encryption where the backup server doesn't read the data...
The list was long before I even got started.

Luckily, it turns out I am not original in my thinking.
So I am testing #borgbackup now and how I can integrate it seamlessly into my #ansible provisioning.

https://www.borgbackup.org/

I just (finally!) cancelled my #dropbox subscription as part of my move away from propritary (esp. American) tech! 🎉

I've been a subscriber since I was a teenager and it has taken me a while to work out how to untangle myself from this one!

(I'm moving to #ProtonDrive and #BorgBackup instead)

#OpenSource #DeGoogling

borgbackup 1.4.4 was just released!

Some important fixes, a few small new features, check the change log please!

https://github.com/borgbackup/borg/releases/tag/1.4.4

#borgbackup #backup #linux #macos #freebsd #openbsd #netbsd

Couldn't get back to sleep this morning after waking up in pain, so I took some time to ease the mental pain of keeping track of what's running where in my #homelab with a new #wiki page. Have a look if you're interested in what I'm running across my main #NAS and two Raspberry Pis.

Hopefully this will serve as a reminder of what config files I really need to put in a central location.

https://yuno.jack-case.pro/bookstack/books/homelab/page/software-and-configuration-inventory

#Documentation #Bookstack #Yunohost #Docker #OpenMediaVault #Backup #BorgBackup

borgbackup 2.0.0 beta 21 was just released!

Please help testing!

https://github.com/borgbackup/borg/releases/tag/2.0.0b21

#borgbackup #linux #macos #freebsd #openbsd #netbsd #omniOS #haikuOS #windows #backup