Storage management in Immich?
-
What's the optimum way to manage the data (app code + uploaded files) and backups (of the app code)?
Currently, i've set the app to use an external Volume as the primary 'Data Directory'.
But, as the Data Directory also includes the uploaded files (which could be hundreds of GBs), it does seem prudent to have the uploaded files stored in a non-regular-backup location.
Initially, I did try mounting a volume and configuring theimmich.json
, but that didn't seem to work.immich.json
->{ "UPLOAD_LOCATION":"/media/<volume name>/data/immich_files", "THUMB_LOCATION":"/media/<volume name>/data/thumbs", "ENCODED_VIDEO_LOCATION":"/media/<volume name>/data/encoded-video", "PROFILE_LOCATION":"/media/<volume name>/data/profile" }
Error log ->
WARN [Api:DuplicateService] Unknown keys found: { "UPLOAD_LOCATION": "/media/<volume name>/data/immich_files", "THUMB_LOCATION": "/media/<volume name>/data/thumbs", "ENCODED_VIDEO_LOCATION": "/media/<volume name>/data/encoded-video", "PROFILE_LOCATION": "/media/<volume name>/data/profile" }
Immich references ->
https://immich.app/docs/guides/custom-locations
https://immich.app/docs/install/docker-compose#step-2---populate-the-env-file-with-custom-values -
@shrey said in Storage management in Immich?:
Currently, i've set the app to use an external Volume as the primary 'Data Directory'.
But, as the Data Directory also includes the uploaded files (which could be hundreds of GBs), it does seem prudent to have the uploaded files stored in a non-regular-backup location.
-
@shrey I think it might be better to just set the data directory and just disable backups for immich instead. As you know, it's still in active development and moving around files will cause things to go out of sync with the database. This will just cause unnecessary headaches if we make this configurable. It is similar to nextcloud in this aspect (whose data directory can also not be configured in Cloudron package)