Recently I have decided that the backup solution I have been using is far too complex for my family to figure out when I die. I began writing documentation on how they can access photos, videos, documents and so on. In that process I thought, I gotta make this simple.
I’m thinking of just having two 10TB drives in RAID 1 on my desktop that get backed up to Backblaze via restic. Backblaze and similar cloud storage providers can send you a copy of your data for recovery. I think I can sufficiently document this process.
This is really good, I just realized I read it a while back, and it prompted me and and a technically competent friend to at the very least be each other’s bitwarden “killswitch” users - forget what it’s called, the person that can take over your vault if you are dead/disappear, it is configurable in different ways, like if they request access and you don’t respond by X days, they get it. We don’t have the same skill set, but are both competent enough to figure it out or find someone that can access everything needed if given all the credentials stored there. I should do more and document, but this is a first good step if shit hits the fan
I just read that README, quite sobering. Now I’m thinking of bus scenario backup plans. Like, there’s stuff that is eventually gonna stop working if left unattended too long, and you just assume you’re gonna be around to maintain it, you know?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
https://github.com/potatoqualitee/eol-dr
This is really good, I just realized I read it a while back, and it prompted me and and a technically competent friend to at the very least be each other’s bitwarden “killswitch” users - forget what it’s called, the person that can take over your vault if you are dead/disappear, it is configurable in different ways, like if they request access and you don’t respond by X days, they get it. We don’t have the same skill set, but are both competent enough to figure it out or find someone that can access everything needed if given all the credentials stored there. I should do more and document, but this is a first good step if shit hits the fan
I just read that README, quite sobering. Now I’m thinking of bus scenario backup plans. Like, there’s stuff that is eventually gonna stop working if left unattended too long, and you just assume you’re gonna be around to maintain it, you know?