15

Hopefully I'm posting this in the right place. I'm planning on using immich for selfhosted photo storage. I'm a bit worried that I may lose all my photos if my drive fails, so I'm planning on running two hdd's in raid 1 in addition to my nvme that I'm running my OS on.

I couldn't find this when I googled it, but is it possible to point immich to store data on a separate internal drive other than the one that the OS is running on?

you are viewing a single comment's thread
view the rest of the comments
[-] ShouldIHaveFun@lemmy.pec0ra.ch 9 points 1 year ago

If you run immich with docker, you can choose any drive/folder for your photos by mounting it at the right location inside the docker container.

However, I would strongly suggest that you also use some other kind of backup beside rest. I personally like restic combined with Backblaze B2, but there are many other good solutions for this.

[-] skates@sh.itjust.works 1 points 1 year ago

I just googled restic, so does it just create a single encrypted backup file you can upload to backblaze b2 cloud storage? I will definitely look into that.

For now, immich is just another safety net. I've got my photos backed up to iCloud photos as well as Google Photos. It's not a price or privacy thing so much as a just in case Google or Apple decides to shut down my account for whatever reason.

I may skip running two hdd's in raid 1 though if restic and b2 can restore all my files if the drive fails. Have you done this before? Is it difficult to restore to a backup?

[-] ShortN0te@lemmy.ml 1 points 1 year ago

Restic does nit create a single backup file. You can either pack the repository in an archive or use restic do directly backup to b2. If i recall correctly b2 is supported by restic directly.

And just to stress that point: backup > redundancy

this post was submitted on 12 Jul 2023
15 points (89.5% liked)

Selfhosted

39251 readers
251 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS