Dotfiles.system VS kopia

Probably using BTRBK. I'm using it for some time now, and it never failed on me. Here are my BTRBK config files for it: https://github.com/rizzini/Dotfiles.system/tree/master/etc/btrbk

My full refind.conf for better visualization.

At least here, root's cron jobs are stored at /var/spool/cron/root. https://github.com/rizzini/Dotfiles.system/blob/master/var/spool/cron/root

PKG_subvol.conf - Clean every 3 days.

Good catch. You really, really should change that behavior. It's not healthy for your SSD. Do it manually or even better, use continuous TRIM setting the discard flag on your fstab like this.

Anbox script bound to META + A keys. I don't need to open some third-party software, like Waydroid's case, so I start it directly using a Systemd service unit configuration file. Besides that unit file, I made a simple script that opens Anbox and closes it if I run the script again. Script. anbox.service file.

BTRBK on the other hand, it's super flexible and holds lots of possibilities. You can, for example, automatically copy the snapshots to another storage device. You can do that even though SSH if you're into that. Here you can find how I set it up on my environment for my ROOT and HOME subvolumes.

I think Kopia would be great for your use case

https://kopia.io/

It has a great system to snapshot files but only store data if it's changed. I use it in an environment where I can't use something like zfs to snapshot data because I don't have the ability to make decisions about what filesystem we're using. It's been amazing, love it so much!

Thanks for the tip on Kopia. Setting it up now, looks perfect.

https://github.com/kopia/kopia

Kopia - GitHub

I've been happy with: https://kopia.io/

Fairly easy to configure, does snapshots to S3 and has a icon in my tray I can watch :)

Btw, kopia is one fine backup tool. Apparently borgbackup is good too.

Kopia is great, though it's worth noting for folks on Linux: non-UTF-8 paths aren't stored correctly [1] and xattrs aren't stored [2]. While most folks probably won't care about the former, the latter can could cause issues (eg. losing SELinux labels makes it difficult to restore a backup of the root filesystem on distros that use SELinux).

[1] https://github.com/kopia/kopia/issues/1764

[2] https://github.com/kopia/kopia/issues/544

I think Kopia [1] is on its way to be that. I am sticking to Restic for now but it seems like the strongest contender.

[1]: https://github.com/kopia/kopia

I used their trial for a bit to test it out with Vorta [1] in a container. Vorta (and Borg) seemed to work fine, until I wanted to restore an archive and I noticed that my recent snapshots were completely empty. Probably because of a misconfiguration on my end though. But it made me look elsewhere. For me backups should be a fire, test and forget solution.

Recently I made the switch to Kopia [2] which seems to have feature parity with Borg (and Restic [3]). It also has a web UI which is way easier to work with than Vorta. And I can easily view, extract and restore individual files or folders from there. This gave me way more confidence about this solution. The only thing I really miss is that I cannot chose different targets for different paths. For instance, with Borg I was able to backup a partial of my Docker appdata to an external source. And I haven't found a way to do this with Kopia. Besides that I'm pretty happy with this solution and I would recommend it.

1. https://vorta.borgbase.com/

2. https://kopia.io/

3. https://restic.net/

There's a few. Off the top of my head

https://github.com/kopia/kopia