You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A concise, battle‑tested tutorial to **restore Immich safely**, validate your backups, and practice disaster recovery without guesswork.
13
+
A short, practical guide to restoring Immich for Docker Compose deployments. It covers validating backups, restoring the database, and performing a test restore safely.
14
14
15
-
> **Read this first** This guide targets **Docker Compose** deployments that follow the **official Immich layout**.**Not supported:** Helm/Kubernetes and non‑standard installers.
15
+
> **Read this first:** This guide targets Docker Compose setups that follow the official Immich layout. Not for Helm/Kubernetes or heavily customized installers.
16
16
17
-
* * *
17
+
---
18
18
19
19
## Quick start (TL;DR)
20
20
@@ -24,106 +24,47 @@ A concise, battle‑tested tutorial to **restore Immich safely**, validate your
24
24
4. Follow [[Part 4. Immich backup restore - Restoring your Database]] to perform the restore on a **clean instance**.
25
25
5. Verify your library; document any errors and fixes.
26
26
27
-
> [!DANGER]
28
-
> > **Data loss risk** Some steps remove volumes and wipe database contents. **Triple‑check paths** before running destructive commands. And make sure you have backed up your <MASTER_DIR> with a [[The 3-2-1 Backup Method]]
29
-
30
-
* * *
31
-
32
-
## Who this is for
33
-
34
-
*[[Self-Hosting|Self-hosters]] running **Immich via Docker Compose**.
35
-
* Anyone who wants a **repeatable restore** and a **quarterly test‑restore** workflow.
36
-
* Users who value **clear checklists**, **safe defaults**, and **fast recovery**.
37
-
38
-
## What you need (at minimum)
39
-
40
-
* Access to your host via **SSH** and basic **CLI** skills.
41
-
* Your Immich **master folder** (e.g., `/volume1/docker/immich`).
42
-
* A recent **database dump** (`*.sql.gz`).
43
-
* Enough free space to stage a second instance for testing (optional but recommended).
*[ ] I have a **full backup** of `<MASTER_DIR>` (including `upload/`).
59
-
*[ ] I verified my **DB dump** exists and is recent.
60
-
*[ ] My **new instance** uses compatible **Postgres** and Immich versions.
61
-
*[ ] I understand how to **stop/start** specific containers with Docker.
62
-
*[ ] I’ve read the **Caution** callouts and accept the risk.
63
-
64
-
* * *
65
-
66
-
## Support & boundaries
27
+
> **Danger:** Some steps remove volumes and will wipe data. Triple‑check paths and backups before running destructive commands.
67
28
68
-
I’ll do my best to provide **1‑on‑1 help** where needed, subject to a waitlist. When contacting me, include the details requested in the PM template (English level, timezone, Immich version, sanitized `docker-compose.yml`, `.env` paths, etc.).
69
-
70
-
71
-
# Request template:
72
-
73
-
# Before you PM me about Immich backup/restore
74
-
75
-
I’m happy to help—just note there’s a waitlist. To speed things up, **include the details below in your first message**.
76
-
77
-
You may contact me at [Reddit](https://www.reddit.com/u/Western-Coffee4367/s/AkRhAaFzd6)or my dedicated immich [Support email](mailto:[email protected])
78
-
79
-
# What to send me (required)
80
-
81
-
***English level:** (Mother tongue/fluent/basic).
82
-
***OK with screenshare/video call?** (Yes/No) *If No, I’ll adapt the tutorial accordingly.*
83
-
***Your Immich version:** e.g. v.140.1
84
-
***Your timezone:** (e.g., Europe/Amsterdam)
85
-
***Are you familiar with SSH/command line?** (Yes/No)
86
-
***Latest DB dump date:**
87
-
***Full paths from your**`.env` (media, upload, etc.)
88
-
***Your**`docker-compose.yml`**(sanitized):***I can’t help without this.****Remove/redact passwords, tokens, and secrets****before sending.*
89
-
90
-
# What we’re doing
29
+
---
91
30
92
-
***Choose one:**
93
-
* New clean install + restore, or
94
-
* Verify your backup and recovery steps for peace of mind.
31
+
## Audience
95
32
96
-
> **Have a full backup of your Immich “master” folder ready.** This reduces the time it takes to help significantly.
33
+
- Self-hosters using Immich with Docker Compose.
34
+
- People who want a repeatable restore process and periodic test restores.
97
35
98
-
#Scope / what I support
36
+
## Minimum requirements
99
37
100
-
***Supported:** Docker Compose deployments that follow the official Immich guidelines.
101
-
***Not supported (for now):** Kubernetes/Helm charts or non-standard installers. *If you didn’t follow the Immich Docker guidelines or those of MariusHosting, or used Helm, I can’t help you.*
38
+
- SSH access to the host and basic CLI skills.
39
+
- The Immich master folder (e.g., `/volume1/docker/immich`).
40
+
- A recent database dump (`*.sql.gz`).
41
+
- Optional: space to stage a second instance for testing.
102
42
103
-
# Privacy & safety
43
+
---
104
44
105
-
* Do **not** share raw secrets. Redact values in `.env` and `docker-compose.yml` (e.g., `POSTGRES_PASSWORD=****`).
For help: include your Immich version, timezone, sanitized `docker-compose.yml` and an indication of CLI experience. See contact links in the repo for support options.
126
67
127
-
* * *
68
+
---
128
69
129
70
**Start here →**[[Part 1. Immich backup restore - Intro]]
Copy file name to clipboardExpand all lines: content/Knowledge base/Self host rabbithole/Immich App/Immich backup and restore/Part 1. Immich backup restore - Intro.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This guide teaches you how to **restore your Immich backup** in a worst‑case s
16
16
> [!DANGER]
17
17
> The instructions in this manual show you how to prepare your Immich instance to be backed up, and which files to take a backup of. You still need to take care of using an actual backup tool to make a backup yourself using the [[The 3-2-1 Backup Method]]
Copy file name to clipboardExpand all lines: content/Knowledge base/Self host rabbithole/Immich App/Immich backup and restore/Part 4. Immich backup restore - Restoring your Database.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ tags:
7
7
- guide
8
8
status: active
9
9
created: 2025-11-16T09:30:16+01:00
10
-
modified: 2025-11-16T16:45:16+01:00
10
+
modified: 2025-11-22T17:33:23+01:00
11
11
---
12
12
13
13
We will restore your backup onto a **new** Immich instance.
@@ -68,7 +68,7 @@ It should look similar to:
68
68
Delete **only the contents** of the DB data folder (keep the folder itself):
69
69
70
70
# If you are already in <MASTER_DIR>
71
-
rm -rf DB_DATA_DIR>/*
71
+
rm -rf <DB_DATA_DIR>/*
72
72
Then verify the `db` folder still exists and is empty.
73
73
74
74
> [!INFO]
@@ -143,14 +143,13 @@ Give the services time to start and complete migrations. Startup will look like
0 commit comments