The Problem Nobody Talks About Until They’re Crying

A photographer I mentored a few years back called me on a Tuesday afternoon in a panic. She’d been shooting commercial work for about three years, growing steadily, getting better clients. She opened Lightroom that morning and her catalog wouldn’t load. Not slow. Not corrupted with a warning. Just gone, as far as Lightroom was concerned. Eighteen months of edits, metadata, keywords, collections, virtual copies, all of it. The RAW files were still on her drives, technically, but without the catalog she’d lost every edit, every client delivery note she’d embedded, every star rating she’d painstakingly assigned.

She had no catalog backup. She didn’t even know Lightroom made one by default, let alone that the default setting backs up only once a week and stores the backup in the same folder as the original.

That’s where most photographers are, and it’s a problem worth taking seriously before it becomes your Tuesday phone call.

What a Lightroom Catalog Actually Is — and Why That Matters

Most photographers treat the catalog like a folder. It isn’t. It’s a database, specifically a SQLite database file with a .lrcat extension, that stores every edit you’ve ever made as a set of instructions rather than pixel changes. When you push a slider in Lightroom, nothing happens to the original RAW file. Lightroom writes those adjustments into the catalog and renders a preview.

This is actually brilliant for non-destructive editing. It’s a liability if you misunderstand what you’re protecting. Backing up your RAW files but not your catalog means you have your negatives but no darkroom work. A 50GB folder of RAW files is useless to a client who needed those processed images last Friday.

The catalog file itself is usually small, often between 300MB and 2GB depending on how many images and previews you’re managing. Smart previews, which let you edit offline without the original files connected, add another layer of data stored separately in a .lrdata folder alongside the catalog. You need to back up both.

The Catalog Structure That Actually Scales

I run one master catalog per year. Not one per client, not one per camera body, not one giant catalog that goes back to 2009. One per year.

The annual structure gives me a manageable file size, clean archiving when the year ends, and fast performance because Lightroom doesn’t have to index 200,000 images every time I open it. Each catalog lives in a folder called LR_[YEAR] on my primary internal SSD, structured like this:

LR_2024/
  LR_2024.lrcat
  LR_2024 Previews.lrdata/
  Backups/

Inside Lightroom, I organize by collection sets named after clients, with sub-collections for each job. Keywords are assigned at import using import presets, not manually after the fact. If it doesn’t happen at import, it doesn’t happen at all, and three months later you’re trying to remember which shoot had the woman in the red jacket.

For import settings, I shoot tethered or card-to-drive. I use a Rename Files preset that outputs ClientName_YYYYMMDD_####, so MerchantBakery_20240318_0042.ARW. File management clarity at the folder level means I can find any image in my system without opening Lightroom at all.

Backup Settings That Are Actually Worth Something

Go to Edit > Catalog Settings > General right now if you haven’t checked this recently. The backup frequency defaults to “Once a week, when exiting Lightroom.” Change it to “Every time Lightroom exits.” Yes, it adds 30 to 90 seconds to your shutdown. That’s the price of insurance.

More importantly, change where the backup goes. The default drops it into a subfolder of your catalog location. If that drive dies, you’ve lost the catalog and the backup simultaneously. I redirect my Lightroom backups to a dedicated folder on a second internal drive. From there, my backup software, I use Carbon Copy Cloner on Mac, mirrors that drive to a NAS and an offsite cloud location through Backblaze at $9/month.

The full chain: primary catalog on SSD, backup on second internal drive, mirrored to a Synology DS223 NAS (around $300 for the unit, plus two 4TB drives), and Backblaze as the offsite layer. Three locations, two physical media types, one offsite. It’s the 3-2-1 rule, and it’s not optional.

I test the restore process the first Monday of every month. Not just checking that the drives spin up. Actually restoring a file. If you’ve never tested a restore, you don’t have a backup, you have a guess.

When the System Saved Me (and When It Didn’t)

My twins were about seven when they got curious about my editing setup. I stepped away from my desk for maybe four minutes. When I came back, one of them had dragged a folder of client proof selects into the trash and emptied it. Not the RAW files, those were fine, but the collection and the exported JPEGs I was about to deliver.

I had the exported files restored from my NAS backup in under two minutes. The collection I rebuilt from the catalog backup in about five. The client never knew. I turned it into a lesson for the kids about dad’s “very boring but very important computer stuff,” and I added a note to my lessons-learned journal: lock the screen, always, even for four minutes.

The journal is something I started at a newspaper, where delivering late wasn’t an option and every mistake had a byline attached to it. I write down what broke, what nearly broke, and what I’d do differently. Catalog management is one of the things that shows up in that journal more than once, always in the context of “could have been catastrophic, wasn’t, here’s why.”

The Catalog Is Your Business, Not Just Your Photos

Your RAW files are raw material. Your catalog is the finished work, the edits, the organization, the institutional memory of every job you’ve done. Treat it like the asset it is, build a backup chain with at least three locations before you need it, and test that chain regularly.

Everything else in your workflow can be rebuilt. That database, if it disappears without a backup, takes your entire editing history with it.