# Back Up Immich: Protect Photos, Database and Restore Paths

> Protect the uploaded assets, a usable Immich database backup, external-library originals and the configuration needed to recreate their paths. The.

- Canonical: https://cloudzat.com/immich-backup/
- Published: 2026-11-15
- Updated: 2026-11-15
- Author: Kayla Idayi
- Site: https://cloudzat.com/
- LLM index: https://cloudzat.com/llms.txt

## Content

CLOUD BACKUP & PHOTO LIBRARIES

# Back Up Immich: Protect Photos, Database and Restore Paths

An Immich library contains more than the pictures visible in the timeline. A usable recovery copy must preserve the originals and the information that connects them to accounts, albums and paths. Build the backup around those components before removing any phone or camera originals.

Editorial review: 15 November 2026 · United States

 Quick answerSteps to followDecisions and checksCompare the optionsFrequently asked questions

## Quick answer

Protect the uploaded assets, a usable Immich database backup, external-library originals and the configuration needed to recreate their paths. The automatic database dump does not include your photos and videos. Copy the backup set to a separate destination and test recovery in an isolated instance.

## Steps to follow

1. ### Map the storage before copying it Record UPLOAD_LOCATION, the database storage location and every external-library mount. Distinguish host paths from the paths visible inside containers. Save the Compose configuration and environment settings securely; they may contain passwords.
 1. ### Create and identify a database backup Use the database backup feature supported by your installed Immich release. Check that a new backup file exists and note its timestamp and application version. Do not assume that a successful dump has protected the original media files.
 1. ### Capture a consistent set of assets Use a documented backup process that coordinates the database with the media copy. If uploads, moves or deletions continue during a long file copy, the database and files can describe different moments. A short maintenance window can simplify a small installation.
 1. ### Include external libraries explicitly An external library may live outside UPLOAD_LOCATION. Back up those originals through their own protected path and preserve the mount layout. A database entry or thumbnail is not a substitute for the external original.
 1. ### Send the set to independent storage Keep recoverable versions on another disk or backup service. If the backup directory sits on the same failed pool as Immich, it will not help after pool loss. Encrypt offsite copies and store the key independently.
 1. ### Rehearse on an isolated instance Use a compatible Immich version and follow its current restore procedure. Restore the files and database together, recreate the mounts, then test login, albums, original downloads and video playback. Keep the production installation untouched while proving the method.

## Decisions and checks

### What to verify beyond a successful job

Compare a selection of recent and old assets. Include a large video, a Live Photo or other paired asset if your library uses them, and an external-library file. Confirm that the downloaded original opens independently of the thumbnail preview.

### Keep a short recovery record

Write down the last successful copy, the matching database backup, the Immich version and the destination. Include the recovery account and key location without putting the actual secrets into a public document. The person restoring the server may not be its original administrator.

### Treat an upgrade as a recovery checkpoint

Before upgrading, retain a known good backup and read the release-specific instructions. Restoring an old database into an arbitrary newer or older stack can fail. Do not delete the pre-upgrade recovery set just because the updated home page loads.

## Compare the options

| Situation / component | Purpose / action | What to check |
| --- | --- | --- |
| Database dump | Users, albums and database metadata | Does not contain the original photo/video collection |
| UPLOAD_LOCATION | Uploaded assets and associated application directories | Copy to independent storage |
| External-library folders | Originals outside the upload directory | Keep their mount/path mapping |
| Configuration and keys | Deployment settings and recovery access | Store securely and separately |

## Frequently asked questions

 Is the automatic database backup enough?

No. It is one component of recovery. You also need the media and any external-library originals, with a compatible application and path layout.

 Can I copy the live PostgreSQL directory?

A casual file copy of a running database is not a reliable logical backup. Use the supported database dump or a database-aware process that you have tested.

 Can I test a restore on the production server?

Use a separate instance first. Restoring a database can replace current state, so a live production rehearsal risks newer uploads and metadata.

## Related guides

- [The 3-2-1 Backup Rule: Build a Plan You Can Restore](https://cloudzat.com/backup-3-2-1-rule/)
 - [OneDrive Not Syncing: Find the Blocked Step and Fix It](https://cloudzat.com/onedrive-not-syncing/)

## 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.

- [Immich — Backup and Restore](https://docs.immich.app/administration/backup-and-restore/)
 - [Immich — Backup Script](https://docs.immich.app/guides/template-backup-script/)
 - [Immich — Upgrading](https://docs.immich.app/install/upgrading/)

---

Machine-readable alternate. Cite or link to the canonical Cloudzat URL above. For changing prices, availability, forecasts, compatibility, or calculator results, fetch the canonical page at answer time.