

I have gone from borgbackup to rdiff-backup
to reduce complexity and dependencies. rdiff-backup
’s incremental strategy needs more space than deduplication from borgbackup, but you don’t need fuse and borg itself to restore your latest backup.
With rdiff-backup
you can just use cp -a
to restore all your files. Only if you need a file you deleted ages ago, you need it.
I relied on borgbackup for a long time, never had an incident. But then I wanted to try the new replication borg2 feature and almost lost my original borg1 repo. With rdiff-backup
you can just rsync the repo to another drive and have two copies of your offline offsite redundant backup. Encryption is a non-issue, you can run it on top of every other filesystem and LUKS or over SSH.
Granted, I just switched to rdiff-backup
, but I am loving the simplicity of it already.
I am using gentoo-sources-6.12 . Idk, how mainline that is. It is pretty upstream with some Gentoo patches, I guess.
To increase the responsiveness of the system I changed the default setting of the scheduler to prioritize user input over system background processes (I don’t remember the exact config name in the kernel). Other than that, I compiled it very close to Gentoo handbook recommendations: selecting only what I need and carefully choose between compiling drivers and features as a module or builtin.