What's the best way to keep an offsite copy of a local borg backup?

I currently use rsync to just fetch the latest version, but running a borg compact on the (space-constrained) original repo results in about 15% of the files being new or changed, so that's a lot of work for rsync on a 500 GB backup.

#borgbackup

I just lost situational (situGUInal?) awareness and accidentally deleted two entire photo albums from my phone gallery thinking they were just two images. And #Syncthing replicated the deletion to all my computers. But, happy ending, not only do I take regular #BorgBackup backups, I also use #btrbk so recovered everything via the snapshots on the laptop within 60 seconds, and of course Syncthing copied them back to the phone immediately.

Check your backups.

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

Thinking about setting up a home #borg server on an unused #RaspberyPi 4.

Questions for the #HiveMind:

• How much RAM does a borg server need to manage about 3TB of backups?
• How big of a USB disk do I need for the / partition for RasbperryPi OS with no GUI?
• Does borg deduplicate files between users' backups, or only within a single user's backups?

#BorgBackup #AskFedi

Streaming #PostgreSQL backups with pg_dump and #borgbackup on #NixOS.

https://blog.linuxw.info/streaming-postgresql-backups-with-pg_dump-and-borgbackup-en.html

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

#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.