Creating a Private Family Photo Archive on a Linux Server

Family photos are irreplaceable data.

Design the archive so the original files remain recoverable even if the photo-management application disappears.

That means preservation first, application second.

Immich can provide the library experience

Immich is a self-hosted photo and video platform with web viewing, mobile uploads, albums, search, machine-learning features and timeline organization.

Its current quick-start path uses Docker and requires at least 6 GB RAM and 2 CPU cores, with more resources recommended for a smoother experience.

Know where the originals live

The photo/video assets are separate from the Immich database.

The database stores important metadata and application state.

Immich's own backup guidance is explicit that database backups do not contain the photo and video assets.

A recoverable system needs both.

External libraries can preserve an existing archive

Immich can index an external photo library stored on the filesystem.

That can be useful when you already have a carefully organized archive and want Immich to provide browsing and search without making the application the only owner of the originals.

External libraries can be mounted read-only if you want to reduce the chance of the application modifying those source files.

Generated data is not the same as originals

Photo platforms may create thumbnails, transcoded video, machine-learning indexes and metadata stored in the database.

Those improve the user experience.

They should not become your only representation of the family photos.

Use a 3-2-1 backup approach

Immich currently recommends a 3-2-1 strategy.

Plan backups for original photo/video assets, the Immich database and configuration needed to rebuild the service.

An automatic database backup on the same server is useful, but it does not protect against loss of the whole machine.

Test a restore

Periodically verify that backup files can be read, database backups exist, photo assets are present and another machine can access the independent copy.

A backup that has never been tested is an assumption.

Think carefully about remote access

A self-hosted photo server is not automatically private.

Privacy depends on server patching, account security, remote exposure, network design, backup security and who has access.

Import slowly

When migrating from phones or cloud providers, keep the original source until the new archive and backups have been verified.

For general self-hosted files, see Hosting Your Own Files Instead of Depending Entirely on Cloud Storage.

A family archive succeeds when the memories outlive the application managing them.