The solution is packaging.

My Immich server performs a nightly backup to a 2tb flash drive labelled "PHOTOS" attached to the router. My partner knows where it is and what it's for, and everyone knows how to use a flash drive.

▲

poidos 4 days ago | parent | next [-]

Are you rotating flash drives and such? I would worry about something happening to me, then she goes to use the flash drive, and the data is corrupt or the drive is fried.

	▲	sheerun 4 days ago \| parent \| next [-]
		This. It is true science how to preserve data long-term. And if you want to encrypt it (e2e or not), you better have very good plan how to recover it when you die
	▲	hamdingers 4 days ago \| parent \| prev [-]
		Nope. I recognize it's a risk, but it still seems like the solution with the least compromises and the highest probability of success. My server sends me notifications for every update with the rsync output so I'll know if any problems arise while I'm around. The last drive in this position lasted 4 years without incident, and I only replaced it earlier this year because it was full.

▲

Modified3019 4 days ago | parent | prev [-]

Is there a way to export things like notes to a sidecar file? Basically need to have photo123.jpg and photo123.jpg_notes.txt available.

I’m trying to archive, document and make accessible family photos, but fear any work I do organizing information in immich may as well be throwing it into black hole.

	▲	hamdingers 4 days ago \| parent [-]
		I'm comfortable trading some metadata for a foolproof handoff of the assets themselves. The library is organized in year/month/day folders so it's navigable that way. I back up the complete Immich filesystem and database, and include a docker-compose.yml, so if it was handed to someone technically inclined they'd have all that.