@borgbackup One final question (I think) before I can finish my Borg/restic writeup that I've been working on for the last days: How stable (as in: safe to use) is borg recreate (in 1.2, if that matters)? I'm asking because the docs for it have the red-and-white stripes, which are supposed to mean "unstable", but that's just unstable as in "the interface may change", right?
And while the docs say "might lead to data loss", they also add "(if used wrongly)".
Ugh, so in one of the replies to my experiments with #BorgBackup and associated tooling, @guerda asked "well, why not #restic?" and turns out, my main reasons against using restic (no compression and no exclude exceptions) are no longer valid, so I'm currently re-evaluating it.
Almost finished my writeup. And you know what? Both are really good.
My decision might boil down to performance against remote hosts and SSH vs SFTP, and whether "rclone serve restic" can save the day there.
The main thing missing from #restic's compression feature¹ is what #BorgBackup calls "auto": try compressing a small part of the file to see if it makes sense at all (i.e. if the file is compressible), and skip compressing that file if it doesn't. Right now, restic can only compress all files during a run, or none.
¹ other than documentation; it's not cool that I had to dig through the source to find the difference between "auto" and "max" compression, and which algorithm it's using at all
As a Mac-user, I actually do not like Time Machine.
I remember using Time Machine on spinning external disks and it did its job whenever I needed something! But it just takes forever nowadays to even launch the backup browser. (Maybe because I have 2TB instead of 500GB disks now?)
Anyone here using #Borgmatic? Are you happy with it?
If you're using another #BorgBackup wrapper and think it's better than Borgmatic, feel free to suggest it (and tell me why it's better.)
Plain Borg simply doesn't quite cut it for me, I'd like to have some kind of declarative configuration that I can share between machines and yet still have minor differences between them. I was about to write my own wrapper, but Borgmatic looks like it could be everything I need.
I've got some corruption on a 4TB Btrfs filesystem. I have all files in #BorgBackup safe and ready to restore, but... I can't figure out HOW to restore them.
OK so today I learned that with #borgbackup you shouldn't forget to run borg compact once in a while. I was wondering why my Mastodon backups took 16TB space...
Also looking into https://torsion.org/borgmatic which looks like a useful toolset around borgbackup. (This will do the compact for me automatically.. ;-) )
#HaikuOS So once in a while you stumble into #Python yay! ;)
This time upstream asked to checkout latest changes for #borgbackup,, seemed that was easy to update.
Time for some checking, earlier I did this with #borgweb, which was still OK, upstream mentioned #Vorta so I wanted to have a look there, #pip to the rescue! So I thought :P
No go on their latest version (requires #pyQt6), prior version seemed to be fine, but then #psutil got in the way, so updating that got me a working #Vorta! :D
is there some #oss#backup app that you can suggest which keeps backing up in the background (always running)?
Preferable something similiar like #borgbackup.
Needs to run on a mac.
I have some family members which ... dont really know much about computers so letting a backup job run periodically or even ask them to start it is a lost cause.