Ferawyn

KeePass. Putting your passwords on someone else's webserver is just asking for trouble.

Various different ways for various different types of files.

Anything important is shared between my desktop PC's, servers and my phone through Syncthing. Those syncthing folders are all also shared with two separate servers (in two separate locations) with hourly, daily, weekly, monthly volume snapshotting. Think your financial administration, work files, anything you produce, write, your main music collection, etc... It's also a great way to keep your music in sync between your desktop PC and your phone.

Servers have their configuration files, /etc, /var/log, /root, etc... rsynced every 15 minutes to the same two backup servers, also to snapshotted volumes. That way, should any one server burn down, I can rebuild it in a trivial amount of time. This also goes for user profiles, document directories, ProgramData, and anything non-synced on windows PC's.

Specific data sets, like database backups, repositories and such are also generally rsynced regularly, some to snapshotted volumes, some to regulars, depending on the size and volatility of the data.

Bigger file shares, like movies, tv-shows, etc... I don't backup, but they're stored on a distributed GlusterFS, so if any one server goes down, that doesn't lose me everything just yet.

Hardware will fail, sooner or later. You should see any one device as essentially disposable, and have anything of worth synced and archived automatically.

I have always preferred TightVNC over the various other VNC flavours. It does only one thing, but does it well, with minimal setup and network requirements.

I have tried RustDesk recently, and the performance when it worked was nice. But I found it too complex to set up across more than a few machines, and ultimately unreliable, with connections failing without any useful error message, an unresponsive relay, weird certificate errors, etc... It needs a couple of years to mature.

I would suggest looking into using WireGuard to wire your various networks and computers together. It works very well most platforms. You can easily give laptops a road-warrior connection, so they always phone home. Then it doesn't matter where they are.

An i2p node. (https://lemmy.world/c/i2p) VPS's tend to have better uptime and lower latency than home connections.

No. USB is not designed to be reliable. It's designed to be plug and play. Don't plug and play with your data.

If I understand correctly, 'Local' is a feed with only posts that were made on the local server. So here on lemmy.world, that would contain only posts to communities hosted on lemmy.world. Whereas the 'All' feed brings in posts from other servers that lemmy.world knows about. So posts from lemmy.ml or beehaw.org will be included. It does seem to take a bit longer to populate the All feed though, and you'll notice posts 'pop' in as you scroll.

I would suggest having a look at podman. It's a drop-in replacement for docker, except it doesn't require a constantly running daemon, it comes in the main package repositories, so you don't have to do the key and repository stuff, and cockpit has a plugin to help manage podman containers.