The 3-2-1 backup rule: why your self-hosted Immich needs it

Every week someone on r/immich posts some version of the same message. The drive died, the RAID did not rebuild, or a container update went wrong, and now the library is gone. Most of these people had something they thought of as a backup. It turned out to be a second copy sitting right next to the first one.
When you self-host Immich, you are the backup department. Nobody else is going to do it for you. The good news is that the rule for doing it properly has been around for decades, and it fits in one line.
What the 3-2-1 rule is
The 3-2-1 rule says:
- 3 copies of your data. The original plus two backups.
- 2 different types of storage. For example, the disks in your server and an external drive, or your server and a cloud storage bucket.
- 1 copy off-site. Physically somewhere else. Not in the same room, not in the same house.
That is the whole rule. It does not tell you which tool to use. It tells you what your setup has to survive.
Each number covers a different kind of failure. Three copies protect you against a single backup being broken, which happens more often than people admit. Two storage types protect you against one class of hardware or software failing in the same way, like a batch of drives from the same production run that all die around the same age. The off-site copy protects you against the events that take out everything in one location: fire, flooding, theft, or a power surge that fries every device on the same circuit.
Why it matters so much for Immich
Immich is a well-built piece of software. It is also a stack of moving parts: a PostgreSQL database, an upload folder full of originals, generated thumbnails and transcoded videos, and a set of containers you update on a regular basis. Immich’s own backup documentation recommends the 3-2-1 rule for exactly this reason.
A few things are specific to Immich and worth knowing.
The database and the files are a pair. Your photos live as files in the upload location. Albums, faces, people, shared links, and descriptions live in the database. Back up only the files and you get your photos back, without any of the work you put into organizing them. Back up only the database and you have a very detailed index of nothing. Immich creates database dumps automatically, but they land in the same upload folder on the same disk. That is a convenience, not a backup, until you copy them somewhere else.
RAID is not a backup. RAID keeps your server running when one disk fails. It does nothing when you delete an album by accident, when ransomware encrypts the volume, or when the controller writes garbage to every disk at once. RAID mirrors your mistakes in real time, and it mirrors them perfectly.
Sync is not a backup either. If your “backup” is a folder that mirrors your Immich library, a deletion on the server becomes a deletion in the backup on the next run. You want versioned or snapshot-based backups, so you can go back to how things looked last week.
Your phone is not a backup. Many people treat the camera roll as the second copy. Then they turn on “free up space” in the app, and it isn’t anymore.
An untested backup is a guess. The only way to know a backup works is to restore from it. Pick a random album once in a while and try to get it back. Do the same for the database on a spare machine. It takes an afternoon, and it is the most valuable afternoon you will spend on your homelab this year.
A typical 3-2-1 setup for Immich looks like this: the library and database on your server (copy one), a nightly versioned backup to an external drive or NAS at home (copy two, different storage), and an encrypted backup to a storage provider or a drive at a friend’s or family member’s place (copy three, off-site). Tools like restic, Borg, or Kopia handle versioning, deduplication, and encryption for you. Pick one and learn how its restore works before you need it.
None of this is hard. It is tedious, and tedious work tends to slip. That is the real risk with self-hosting. Most people know how to make backups. They stop checking whether the backups still run.
Or let PixelUnion handle it
If you would rather spend your time on your photos than on your backup scripts, this is the part we do for you. Your library lives on our primary storage cluster in Falkenstein, Germany. We run regular backups to a separate cluster in Finland, far enough away that a problem at one location does not reach the other. Both clusters are encrypted, and the encryption keys are kept on separate infrastructure. Neither storage provider can read your files. Monitoring, updates, and making sure the backups keep running are our job, not yours.
We are a small team, and we will not promise you that nothing can ever go wrong. What we can promise is that we take this seriously and keep working at it. You can read exactly how we store, encrypt, and back up your data in our help center article on How we keep your data private and secure.
Start free with PixelUnion →
Cover photo by Curated Lifestyle on Unsplash+.