🧠My Second BrainV4🧠

Part 0. Immich backup restore - Frontpage

2 min read

A short, practical guide to restoring Immich for Docker Compose deployments. It covers validating backups, restoring the database, and performing a test restore safely.

Read this first: This guide targets Docker Compose setups that follow the official Immich layout. Not for Helm/Kubernetes or heavily customized installers.

Quick start (TL;DR)

  1. Review Part 2. Immich backup restore - Getting Started and confirm prerequisites.
  2. Make a backup of the complete <MASTER_DIR> For a correct backup strategy, (see The 3-2-1 Backup Method).
  3. Ensure you have a recent DB dump and follow the [Part 3. Immich backup restore - Basics] under upload/backups/.
  4. Follow Part 4. Immich backup restore - Restoring your Database to perform the restore on a clean instance.
  5. Verify your library; document any errors and fixes.

Danger: Some steps remove volumes and will wipe data. Triple‑check paths and backups before running destructive commands.

Audience

  • Self-hosters using Immich with Docker Compose.
  • People who want a repeatable restore process and periodic test restores.

Minimum requirements

  • SSH access to the host and basic CLI skills.
  • The Immich master folder (e.g., /volume1/docker/immich).
  • A recent database dump (*.sql.gz).
  • Optional: space to stage a second instance for testing.

Contents

Preflight checklist

  • I have a full backup of MASTER_DIR (including upload/).
  • A recent DB dump is available and verified.
  • I can stop/start containers and understand which volumes will be affected.
  • I will perform restores on a clean or test instance first.

Support

For help: include your Immich version, timezone, sanitized docker-compose.yml and an indication of CLI experience. Contact: jpar99redditsupportb.steersman452@passmail.com

Start here → Part 1. Immich backup restore - Intro

Graph View

Backlinks