Thanks for listing this overview and worst case scenario. I can say, for myself, that my current setup covers this situation. Everything is immediatly synced to

Thanks for listing this overview and worst case scenario. I can say, for myself, that my current setup covers this situation. Everything is immediatly synced to my server located offsite, through IPSEC, meaning I have at every time at least two copies of data that are physically separate. My password manager needs a password file and key. the key I remember, the password file is in my encrypted ZFS volume on my server. If my phone (dies), I can still get the password file from my laptop or from the server; if the server dies, I still have it on my laptop or phone. It is extremely unlikely that all three die at the same time. Yet, even for this scenario, I have a printed out list of password of my password manager, hidden at a location that is usually inaccessible. Of course, I follow the 3-2-1(-0) rule, providing additional piece-of-mind beyond that "worst case". So yes, I agree fully: Prepare for worst (and hope for best). For anyone thinking about self-hosting, I suggest to place your server not at your main place - host it offsite (e.g. at your parents house). Makes you also better in remote work and produces overall more stable systems (because driving 100km is a painful motivator).