NaibofTabr

Beyond your eventual technical solution, keep this in mind: untested backups don’t exist.

I recommend reading some documentation about industry-leading solutions like Veeam… you won’t be able to reproduce all of the enterprise-level functionality, at least not without spending a lot of money, but you can try to reproduce the basic practices of good backup systems.

Whatever system you implement, draft a testing plan. A simpler backup solution that you can test and validate will be worth more than something complex and highly detailed.

Er, wait, are you using Syncthing for its intended purpose of syncing files across devices on your local network? And then exposing that infrastructure to the internet? Or are you isolating Syncthing instances?

and you have to choose to boot into desktop mode to even mess with anything.

You say that like it’s a bad thing, but I think having the two separate modes is a fantastic setup. You get basically a console experience, smooth and straightforward and easy to use for just playing games, and you still have access to the underlying system anytime you want.

“We do not break userspace.” ~ Linus Torvalds

I would always argue that any distribution which does not prioritize this principle is a hobby project, not a serious distribution for end users.

Which is fine, hobby projects are good, but they should be labeled accordingly to properly set user expectations.

• a few git repos (pushed and backup in the important stuff) with all docker compose, keys and such (the 5%)

Um, maybe I’m misunderstanding, but you’re storing keys in git repositories which are where…?

And remember, if you haven’t tested your backups then you don’t have backups!