I treat Immich like a frontend. I have photos in Nextcloud, plus local and remote backup (1 2 3 style). Then Immich is set to absorb the photos from Nextcloud, and the photos are exposed read-only to Immich so it can’t damage anything.

Haha this was my first thought too.

Immich is very clear: “⚠️ Do not use the app as the only way to store your photos and videos.”

In that case, you have your content elsewhere. Make a backup of relevant volumes and a database dump (for your albums and such) and then try updating. Roll back if it doesn’t work. If if you don’t have much in the way of Immich meta data, and the upgrade didn’t work, then you could just start from scratch and re-import your content.

Everyone knows you don’t upgrade to a X.0 release. Got to wait for X.1 at least.

I used to have a Play developer account and it felt like every month they would email me saying if I don’t follow some action my apps would be removed. Sometimes it was based on some law change, but then they would just remove you in that jurisdiction. Many were much more arbitrary things. I have trouble remembering and don’t use that account or email address anymore but it was things like setting an age rating or some new flag they introduced. If you didn’t do it in a certain amount of time then your app got removed.

I don’t remember one about updates but it wouldn’t surprise me, otherwise it could just be one of many of their arbitrary requirements.

I also don’t mind slow updates in general, but when people are reporting issues and getting no response then that does put me off a bit.

It’s a launcher, so regular updates are less important, but it does still concern me a bit.

My other launcher is KISS 😆 I gave TinyBit a go, I’m not sure i like the look. I feel like KISS looks more… polished? Modern? Not sure of the right word.

Should I be concerned it was last updated 9 months ago?

Well you wouldn’t have been able to do docker compose up if it was like that, right? So it must have been changed while it was running.

Lemmy-UI and the backend are completely separate, so if the UI is not working apps can still connect to the back end if that’s running.

Wow, a lot of variation in this thread!

I get all my data to my server, then from there I have borgmatic do incremental backups to a backup drive on the same machine (nightly cronjob).

From there I use Rclone to get the encrypted borg backup to Backblaze B2 for cloud storage.

So for 3 2 1, my 3 copies are the original, the local backup, and the cloud backup.

My 2 media are local hard drives and cloud storage (I think it’s fair to consider this a different kind of media).

And my 1 offsite is the cloud backup.

Now I’m dumb and have a fear of screwing something up so I have also started burning M-Discs of my critical data (everything except TV/movie/music stuff I can redownload). Though this was a lot more expensive than I was expecting, because of aforementioned me being dumb I already screwed up two discs (they are write once). I’m also doing two copies of each disc.

Also I have photos/home videos additionally stored in ente, they are super important to me and I wanted a separated copy someone else is looking after.

Yes, when writing a post you can enter a custom thumbnail URL. A relatively recent feature, sh.itjust.works is on 0.19.5 and I thought it was from earlier than that so try starting a post on the website and you should see it.

What makes you say they are shorter life span? The 25GB and 100GB both have the same “several hundred years” claim.

Thanks, I missed that post! Looks like the comment section would have answered a lot of my question.

In the end I have pulled the trigger and bought an M-Disc capable burner and a stack of M-Discs, so I’m gonna give that a go and see how it works out.

🐑

Sweet, thanks, I think that’s a good plan. I am thinking duplicate disks, one on site one off site. I do have a cloud backup, but if I die in a house fire then having the offsite disks is a much better solution than the random B2 bucket.

Thanks for the help 🙂

Seems the only M-Disc capable writer I can find locally is a portable USB-C connecting one, so if I go with it I’ll probably just store it with the discs. In theory M-Disc is supposed to be resistant to the kinds of things that destroy regular CDs, but making a second copy does sound like a good idea. I could even store the second copy somewhere else (another house) to protect against fire. I have cloud backup but you never know what’s going to happen over 50 years. Or if I die in the fire and no one knows I have the cloud backup.

Like this? https://www.pbtech.co.nz/product/DVWVER4618789/Verbatim-43888-External-Slim-Bluray-Writer-Ultra-H

That’s NZD by the way, conversion rates are terrible at the moment so about halve it for USD, seems in the price range you said.

The idea is that I’d swap out drives every 5 years or so. If USB A is no longer in use I’d swap out at that point for something newer. Plus the drives would be powered on every year for the update, it’s just the point that I stop doing it (too old/hit by bus/etc) that the clock would start ticking.

I do like the M-Disc idea though. Probably a similar price, and more in line with the shelf-stable solution I was looking for.

Everyone is saying to avoid flash memory. It doesn’t store well.

Another suggestion given is M-Disc, which might be a better option because then anyone should be able to throw it in a CD drive and load it without having to worry about the format of the drive and things like that. And even if CDs are not that common anymore, I think people will still know what they are and be able to find a way to load it even in 50 years. Like if someone found a cassette tape today (I know they were common much less than 50 years ago, but it’s hard to find an example since records came back into fashion). Plus M-Discs are designed for long term storage, so I could worry less about bitrot and files getting corrupt etc. They are write once so I’m not going to write over existing content.

Yeah it’s an interesting thought. They seem to come up to 100GB capacity, but the wikipedia page claims (with a [dubious] qualifier) that you need some sort of special higher power burning device to write to M-Disc.

I don’t have an optical drive at the moment. Would I just pick any rated for BDXL?

Yeah since then I’ve been convinced I need two drives mirrored under zfs, which should handle that scenario.

You are the first person who has recommended SSD for cold storage. Everyone else (including what I’ve googled) says HDD for cold storage, just spin up every year or two and they will be fine. Can you point me at further reading?

Don’t worry, I’ll SMART check the drives each year as I update as required.

As for types of drives dying out soon, I can reassess the situation every 5 years when I do drive replacement. I would be confident 2.5" drives will still be readable in 5 years.