pop VS Duplicacy

More info here

General issue reports can be submitted to https://github.com/pop-os/pop

One of my favorites was this one where they told us:

Using controllers with Steam's flatpak is impossible without steam-devices. Installing steam-devices with apt also installs Steam's .deb. Uninstalling Steam's .deb completely removes PipeWire. I have found this issue on GitHub from six months ago, but it hasn't been fixed yet. I'm surprised there are still issues with Steam on Pop!_OS after what happened last time.

I have experienced a similar problem as this issue

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