Home » CloudZat UK » Set Up Immich on Unraid: Choose One Deployment and Protect App Data

Set Up Immich on Unraid: Choose One Deployment and Protect App Data

CLOUD BACKUP & PHOTO LIBRARIES

On Unraid, the template and Compose routes can describe different container arrangements. Pick one maintained method and keep media, database and app configuration mapped to durable storage.

Editorial review: 15 November 2026 · UK

Quick answer

Use the current release’s Compose files, put PostgreSQL on suitable local storage and test a small library before importing everything. The current requirements specify 6GB RAM minimum, 8GB recommended and at least two CPU cores.

Steps to follow

  1. Before you start

    Choose the current Compose release or a maintained template and record its dependencies. Identify the actual pools holding media and database data. Protect the environment file and keep existing originals outside the experimental deployment until a complete recovery test passes.

  2. Set up the right scope

    Check the current Immich Unraid community guide and its Compose route. Prepare persistent app-data and media paths, with PostgreSQL on suitable local storage. If choosing a Community Applications template, follow that template’s current database dependencies instead of mixing it with an old Compose example.

  3. Apply the relevant settings

    For the Compose route, download docker-compose.yml and example.env from the official release links into a new project directory, renaming example.env to .env. Set UPLOAD_LOCATION, a local DB_DATA_LOCATION and a suitable strong DB_PASSWORD. Template users should instead apply that maintained template’s documented storage, secret and dependency settings through its own controls.

  4. Complete the first run

    For Compose, run docker compose up -d from the project directory, then inspect docker compose ps and logs. For a template deployment, use its documented deployment and log controls. Complete account setup, upload a few originals and test downloads. Protect media and database before a full import or upgrade.

Decisions and checks

The limitation that matters

A share’s cache/pool policy can change where data physically lives. Confirm database storage and ownership, and include app data in backups. Do not change database images or remove volumes merely to match a different tutorial.

How to verify the result

Restart the deployment and confirm accounts, albums and originals persist. Test a large video, phone upload and an isolated restore. The automatic database dump alone does not contain the media.

Keep the result reliable

Review pool capacity, share placement and backup coverage after storage-policy changes. Before upgrades, retain a consistent database and media set; afterward test both a new phone upload and an original already in the library.

Keep the Unraid deployment and its recovery data consistent

Pick one maintained deployment description

The Unraid community route and a Community Applications template can package Immich differently. Decide which supported instructions you are following and retain the corresponding release files together. Do not replace a database image or dependency simply because another tutorial lists a different one. Start by recording Unraid version, deployment method and the actual Immich version. Check the current Immich requirements for your processor architecture, memory and storage, including any major-version changes. A container can start far enough to show partial logs while still lacking a required capability. Read those errors before changing unrelated networking or permissions. Use a separate project directory for a new Compose installation so existing configuration is not overwritten.

Understand where an Unraid share really stores data

A logical share name does not by itself identify the physical pool holding every file. Review primary and secondary storage settings and mover behavior for the media and application data. Keep PostgreSQL on suitable local storage; a network share is not an acceptable database location. A large array with free capacity does not prevent a smaller selected pool from filling. Check the actual data location and available space, not only the server's aggregate figure. If a storage move is needed, follow Unraid's procedure and stop affected services as required so active database files are not treated as an ordinary document copy. Preserve the previous configuration and a valid backup before the move.

Trace Compose paths from the project to the disk

The environment file defines locations used by the release's Compose configuration. Check UPLOAD_LOCATION and DB_DATA_LOCATION against real host paths, including the effect of relative paths when the project folder moves. Keep the environment file protected because it contains sensitive settings. Set the database secret according to the current installation instructions rather than improvising characters that the supplied configuration cannot handle. After deployment, inspect the containers' actual mounts and confirm the expected files appear on persistent storage. Do not regard the container's writable layer as the archive location. Recreating a service should preserve its external data; it should not silently create an unrelated empty library under a different host directory.

Prove the basic media path before adding accelerators

Complete account creation and upload a deliberately small selection. Test a photo download and video playback, then confirm the same collection after a normal restart. Introduce hardware acceleration or advanced external-library arrangements only after that baseline works. If an optional processing service fails, keep its error separate from ordinary upload and database health. Changing several variables at once makes it difficult to distinguish a media-format issue from a broken mount or unsupported acceleration setting. Check the actual phone's server address too: the Unraid dashboard, local web page and remote mobile app can use different access routes. A successful administrative login is not proof that mobile uploads reach the intended instance.

Back up the library, not just a convenient app-data folder

Determine what your chosen app-data backup tool actually includes and how it handles running services. Immich needs database state and the corresponding media files, plus any separately mapped external originals. Its automatic database dump is only one piece. If photographs live in another share, a completed app-data job may leave them completely outside its scope. Keep a dated record of the dataset and share mappings and test recovery into an isolated deployment. Confirm users, album membership and a complete original download. Avoid pointing the recovery instance at live writable media because the purpose is to validate the copied recovery set without modifying the working library.

Upgrade with a clear stop point and rollback plan

Read the release notes for the actual version jump and make a usable backup before replacing services. Current Immich guidance recommends updating mobile clients before the server; check compatibility and instructions for the transition you are making. Do not assume that downgrading a container image reverses a database migration. If an upgrade fails, preserve logs and the current state before choosing the documented recovery route. Keep the release files and environment settings that describe the last working setup. After a successful upgrade, test a new upload and an older original as separate checks. A working empty account or fresh test image alone would not show that the pre-upgrade library survived intact.

Example: the pool fills while the array has room

Suppose uploads stop despite a dashboard showing substantial free array space. Identify the share and pool receiving the actual upload, then inspect that pool's capacity and policy. Do not repeatedly re-import the same collection or delete PostgreSQL files to create space. Decide whether to free legitimate expendable data, expand the intended storage or perform a controlled move with backups. After the correction, upload one new file and confirm where it physically lands. This turns a vague storage error into a specific placement issue and prevents a second unexpected full pool after the next restart or mover run.

Compare the options

Situation / component Purpose / action What to check
Array has room but uploads fail Check the actual writing pool Share placement and free space are distinct
Project directory moved Inspect relative paths and mounted data Do not populate a newly empty database by mistake
App-data backup completed Check separate media shares too Database dump alone excludes photographs

Frequently asked questions

Can I mix the database from another template?

Follow the selected deployment's current dependencies and documented migration procedure. A database image change is not a cosmetic substitution and may require a specific recovery or migration path.

Should I update the server before the phone apps?

Current Immich upgrade guidance recommends mobile clients first, followed by the server, while checking the release notes for the specific transition. Do not assume an image downgrade reverses database changes.

Official documentation

This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.

Scroll to Top