Bup VS Duplicacy

The presented idea (one folder per commit, as FUSE fs) seems indeed largely impractical.

But there are good uses for mountable "git like" repos. For example for backup systems.

https://github.com/bup/bup

For example bup

https://github.com/bup/bup ?

Recently testing bup https://bup.github.io

You may really like https://github.com/bup/bup if you want something a bit more modern but in the same style

That's really good to hear! They got a (well deserved!) 100M investment recently. I didn't know it until recently, but apenwarr made some of my favourite tools (sshuttle, bup) and now tailscale! If you come across the podcast again, please post the link, I'd love to listen to it.

https://bup.github.io/

I have been having great luck with incremental backups with the very similar named Duplicacy https://duplicacy.com/

Pro: No need for a special index database. The chunks are placed in the file system. This explains it in greater detail. Seems to place great emphasis on reliability, which is important for me. Versioning is also supported.

Having all your data in one place isn't wise though, so I am planning on storing encrypted backups on Dropbox and Backblaze B2 using Duplicity so that I am following the 3-2-1 backup rule.

I tried a bunch of different ways but ultimately settled on Duplicacy [0].

It runs inside a Docker container and backs up both my data as well as configurations like my docker compose file and smb.conf.

Off site storage was Backblaze B2, but I moved to Hetzner. Likely will move back just because B2 is cheaper and a bit faster for my region.

Another layer of backup I do is use Duplicacy to backup to a portable hard drive occasionally that I keep off site.

[0] https://duplicacy.com/

Duplicacy

I use Kopia and works well. Have also used this https://duplicacy.com