5 ms·

This is the one photo manager that I have my eyes on, I'm just worried about critical bugs, I've seen some issues reported on github with losing data, like this

by dsego 1y ago

This is the one photo manager that I have my eyes on, I'm just worried about critical bugs, I've seen some issues reported on github with losing data, like this one on the mobile app. https://github.com/immich-app/immich/issues/21936 https://github.com/immich-app/immich/issues/21936 Not sure what to say, could be a very very rare edge case, but it's not very reassuring.

InsideOutSanta 1y ago
I've been using Immich for a year now and haven't lost a single image. Having said that, if you self-host something like this, you're responsible for making backups. The actual photos uploaded to Immich are stored in the file system as regular files. Any other data that Immich can't easily recreate is stored in Postgres, which it automatically dumps once a day. So if you back up your image files and your Postgres dumps, you can always recreate your library.
- darkest_ruby 1y ago
  Can you pls share the paths of folders to be backed up?, especially the raw image files
  - InsideOutSanta 1y ago
    Immich has documentation here: https://docs.immich.app/administration/backup-and-restore/ https://docs.immich.app/administration/backup-and-restore/ All relevant files are stored in your UPLOAD_LOCATION which you defined in your .env file (if you deployed immich via Docker Compose). The files you absolutely need to back up are in: - UPLOAD_LOCATION/upload ← Contains your images - UPLOAD_LOCATION/backups ← Contains your postgres dumps You should also back up these two directories: - UPLOAD_LOCATION/library - UPLOAD_LOCATION/profile They're not strictly necessary, but it makes it easier to restore the same setup.
    - darkest_ruby 1y ago
      Thank you, that's very useful
teekert 1y ago
The issue you linked was close with a PR 1 hour ago :D Still not nice, I've always had all of Immich in a ZFS dataset with regular snapshots. Then you can always roll back. I've only had to use it when I wasn't happy with some large import though.

by dsego 1y ago

InsideOutSanta 1y ago

I've been using Immich for a year now and haven't lost a single image. Having said that, if you self-host something like this, you're responsible for making backups. The actual photos uploaded to Immich are stored in the file system as regular files. Any other data that Immich can't easily recreate is stored in Postgres, which it automatically dumps once a day. So if you back up your image files and your Postgres dumps, you can always recreate your library.

darkest_ruby 1y ago
Can you pls share the paths of folders to be backed up?, especially the raw image files
- InsideOutSanta 1y ago
  Immich has documentation here: https://docs.immich.app/administration/backup-and-restore/ https://docs.immich.app/administration/backup-and-restore/ All relevant files are stored in your UPLOAD_LOCATION which you defined in your .env file (if you deployed immich via Docker Compose). The files you absolutely need to back up are in: - UPLOAD_LOCATION/upload ← Contains your images - UPLOAD_LOCATION/backups ← Contains your postgres dumps You should also back up these two directories: - UPLOAD_LOCATION/library - UPLOAD_LOCATION/profile They're not strictly necessary, but it makes it easier to restore the same setup.
  - darkest_ruby 1y ago
    Thank you, that's very useful

teekert 1y ago

The issue you linked was close with a PR 1 hour ago :D Still not nice, I've always had all of Immich in a ZFS dataset with regular snapshots. Then you can always roll back. I've only had to use it when I wasn't happy with some large import though.