oldsysops (@oldsysops@social.dk-libre.fr)

1 ★ 1 ↺

oldsysops » 🌐 2026-02-22
@oldsysops@social.dk-libre.fr

@nobodyinperson@fosstodon.org @Atemu@darmstadt.social I'm in the process of doing the same, I've just converted a ext4 to #btrfs to do that. I pretty sure that a disk snapshot is suffisant (and i'll go with it). at work we can't/don't stop the service during backup (rsync+#borg). we do have another bckup strategy for postgresql backup (#pgbackrest).

for #selfhosting, it will be enough,i'm confident that my service can endure a powercut, so snapshot will be fine.

i haven't figured out how i will manage off-site backup, maybe export a tar from borg ? or rsync the repo even if it's not advised.

...

Plus anciens…

Yann Büchau » 🌐 2026-02-22
@nobodyinperson@fosstodon.org

@oldsysops @Atemu Offsite borg backup is easy, it can just back up to an ssh remote. Btrfs can also send snapshots incrementally elsewhere (btrfs send) and btrbk apparently can help with that.

artlog » 🌐 2026-02-22
@artlog@agora.l0g.eu

@oldsysops @nobodyinperson @Atemu

I do offsite backup with borg using ssh:// and another using restic + s3 ( still minio have to migrate this to garage);

With #yunhost it is quite easy, with borg application ( https://github.com/YunoHost-Apps/borg_ynh ). Two different yunohost server can cross bakcup one on the other using borg_app / borg server.

artlog » 🌐 2026-02-22
@artlog@agora.l0g.eu

@oldsysops @nobodyinperson @Atemu

I will see if i can set a snapshotable filesystem too, i know friends are doing this with #zfs, #btrfs should achieve smae purpose.

And yes it should work else it could not be called snapshot. What bother me is memory footprint of such solution i doubt it is free lunch ...

...

Zimmie [he/him] » 🌐 2026-02-22
@bob_zim@infosec.exchange

@artlog @Atemu @nobodyinperson @oldsysops With copy-on-write systems like ZFS or btrfs, the snapshot itself is just the filesystem tree as it existed at the point when the snapshot was taken. It’s not even really a copy of the whole filesystem tree, as the tree itself is also copy-on-write.

As such, the additional footprint of a snapshot in RAM and on disk is negligible. It holds references to the old storage records, but it doesn’t make new copies of them. As your current state diverges from the snapshot, the storage it uniquely consumes grows. They really are free to create, and they really do consume basically nothing to keep around for a few hours.

Rainer [he/him] » 🔓 2026-02-22
@Kaffee_Junkie42@norden.social

@oldsysops @nobodyinperson @Atemu > i haven't figured out how i will manage off-site backup, maybe export a tar from borg ? or rsync the repo even if it's not advised.

I used borg at one time, but have been using restic and resticprofile for some time now.

borg and restic are similar in their operation, so switching backup scripts was relatively easy for me.

When copying borg repos, I had the problem that an error message appeared, but it could be ignored:

``` (1/3)