btrfsmaintenance VS kopia

Take a look at setting this up for your distro: https://github.com/kdave/btrfsmaintenance

Your distro might already have this https://github.com/kdave/btrfsmaintenance installed or in the repos

Is there a btrfs management interface that can be accessed/used remotely? I'm talking about an (independant - not a distro) interface like Rockstor or Truenas Scale. I've been searching until my eyes bug out of my skull and I can't find anything. Good peeps of reddit, please am I missing something? I've found plenty of great projects but not what I'm looking for: snapper-gui - single purpose/not remote snapper - single purpose / not a gui and I hate it (sorry) yast - distro specific https://github.com/yourbsod/btrfs-gui - vaporware? timeshift / autosnap - local only and single purpose btrfs-assistant - not remote https://github.com/kdave/btrfsmaintenance - different purpose and not a gui buttermanager - I was unable to try but seems to require grub-btrfs

The btrfsmaintainence project also has services that cover scrub along with other services you might consider running regularly which are set up to not conflict and run at the same time.

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