For a long time, storage felt simple.
Shoot. Import. Organize. Copy everything to a drive.
Then make another copy.
I used Carbon Copy Cloner to maintain those backups, first with portable drives and later with a Drobo 8D. The problem was not that I had no backup strategy. The problem was that the archive itself kept growing.
Eventually, I had somewhere around fifteen to twenty portable hard drives.
The files were organized. There were backup copies. But the archive was fragmented across physical devices.
I could not see everything at once.
I could not access everything at once.
And managing the storage was starting to become work of its own.
That was when my thinking changed.
I stopped treating the archive as a collection of folders and drives and started thinking about it as infrastructure.
This is not the only way to build a photography archive. It is the system I developed around the way I actually work.
The folder structure still matters
Changing the storage system did not make basic organization less important.
If anything, it made it more important.
One thing I have kept consistent through different drives, computers, applications, and storage platforms is a date-first naming convention:
YYYYMMDD_Project_Subject_Detail_###
For example:
20260822_FashionCampaign_Model01_Look01_001
The date gives me natural chronological sorting. The project, subject, and detail provide context. The sequence number keeps individual files in a predictable order.
More importantly, the filename still means something without Lightroom.
I can look at the same file through Finder, Synology File Station, Lightroom, or whatever application I might be using years from now and still understand what I am looking at.
That led to a simple rule I have come to value:
The archive should still make sense when the software changes.
Software is a useful layer on top of the archive.
It should not be the only thing making the archive understandable.
Centralizing the archive solved more than capacity
Portable drives worked until the number of drives became part of the problem.
Moving to a Drobo 8D was my first real step toward centralizing the archive.
Instead of remembering which project lived on which external drive, I could keep far more of the work together. I continued using Carbon Copy Cloner for backup, but the archive itself became much easier to navigate and manage.
For a while, that worked well.
Then Drobo stopped producing its hardware, and compatibility and support on the Mac side eventually became a problem.
That experience changed the way I thought about storage again.
A long-term archive does not only need to survive a failed hard drive. It also has to survive:
- New computers
- New operating systems
- Changes in software
- Changes in interfaces and connectivity
- Even the company behind the hardware disappearing altogether
The files may need to last much longer than any individual storage platform.
That experience eventually led me to Synology.
Today my setup consists of a smaller Synology DS218+ and two six-bay DS1621+ units.
The two larger systems handle photography, video, design, and the other files that make up my working creative archive. One is the primary system. The other is its local backup.
The smaller DS218+ has a different job. It handles documents and mobile-photo backup, including the things where remote access is actually useful.
The important change was not simply switching from one storage brand to another.
It was giving different parts of the system different responsibilities.
My computer is the workstation, not the archive
Lightroom remains at the center of my photography workflow.
But Lightroom and the archive do not need to live in the same place.
My Lightroom catalog lives on the Mac’s internal storage.
The original image files live on the NAS.
Lightroom references those originals across the network.
That separation is intentional.
The Mac is where I work.
The NAS is where the archive lives.
If I replace the computer, I should not also have to rethink where years of photography belong.
The workstation can change far more frequently than the archive.
That distinction became more important as the amount of work increased.
I no longer want the computer, the editing application, and the archive to behave as though they are the same thing.
They are different parts of the system.
The archive has to be usable, not just safe
Archiving often gets discussed primarily as a protection problem.
Keep another copy.
Use redundant drives.
Make sure nothing disappears.
All of that matters.
But there is another side of archival storage that is just as important to me: retrieval.
If an image is safely stored somewhere but retrieving it means finding the correct portable drive, connecting it, mounting it, and searching through it, the file may be protected without being particularly accessible.
That becomes increasingly important across years of work.
I regularly need to revisit older projects, pull an image again, compare previous work, find a reference, or locate something that suddenly becomes relevant.
Centralizing the archive means years of photography remain part of one accessible body of work rather than becoming isolated pieces of history sitting on separate disks.
The value of the archive increases when finding something old is ordinary rather than exceptional.
Backup is a different job from storage
Centralizing everything introduces an obvious responsibility: the archive cannot depend on a single device.
All of my NAS systems use RAID 5, which provides redundancy against a single drive failure.
But I do not consider RAID a backup.
The rest of the protection comes from several layers that serve different purposes:
| Layer | Role |
|---|---|
| RAID 5 | Keeps the NAS running if a single drive fails |
| Primary DS1621+ | Main working archive for photography, video, design, and other creative files |
| Second DS1621+ | Separate local copy of the primary archive |
| Snapshots | Fast recovery from recent accidental deletions or unwanted file changes |
| Hyper Backup | Backs up the primary NAS to the second NAS |
| Time Machine | Backs up the Mac to the NAS |
| Future off-site backup | Would protect the archive from a loss affecting both NAS units in the same location |
The distinction matters because redundancy, backup, and recovery are not the same thing.
RAID helps keep the primary system available when a drive fails. Hyper Backup moves a backup of the archive to the second NAS. Snapshots give me a faster way to recover from recent changes, while Time Machine protects the Mac itself.
There is still one meaningful gap in the system.
Both large NAS units currently live in the same physical location.
An off-site copy would add protection against a loss affecting both systems at once.
I would rather acknowledge that limitation than describe the system as more complete than it is.
Access is also a design decision
A NAS makes remote access possible.
That does not mean every NAS needs to be remotely accessible.
My main photography archive is intentionally kept internal to my network.
I could make it available remotely, but for the bulk of my creative archive I do not have a strong enough reason to introduce that additional exposure.
The smaller DS218+ is different.
I use it for things like documents and mobile-photo backup, where being able to connect while I am away is genuinely useful.
Same technology.
Different purpose.
Different access decision.
I think that distinction applies to systems far beyond storage.
The fact that a tool can do something does not mean every capability needs to be enabled.
Sometimes good system design is as much about deciding what not to add as deciding what to add.
The tool is not the archive
I use Synology now because it gives me the centralized access, flexibility, and protection my archive currently needs.
Before that, Drobo solved the problems I had at the time.
Before that, portable drives did.
I do not expect the Synology hardware sitting in my system today to be the final storage platform I ever use.
That is precisely why I do not want the archive itself to depend too heavily on it.
- The naming convention matters
- The folder structure matters
- The relationship between Lightroom and the original files matters
- The backup strategy matters
- The ability to recover matters
- The ability to migrate matters
The hardware is one layer underneath all of those decisions.
That may be the biggest change in how I think about archival storage.
I used to think the archive was where the folders lived.
Now I think the folders are only one component of a larger system.
A good archive should outlive the current setup
Photography generates a lot of data, so storage capacity is usually the first problem people notice.
How many terabytes do I need?
How many drives?
How large should the NAS be?
Those are necessary questions.
But once an archive becomes large enough, I think they become some of the less interesting ones.
The questions I care about more are:
- Can I find the work?
- Can I still access it when the computer changes?
- Can I recover it if something goes wrong?
- Can I move it when the storage platform eventually changes?
- Will the organization still make sense years from now?
Those questions have influenced my system far more than simply buying increasingly larger drives.
The technology isn't really the point
The NAS is useful, but it is not the lesson.
The useful part is having a system where storage, organization, access, and backup are no longer decisions I have to remake every time I work.
When that infrastructure is working properly, I think about it less.
I can import a project without deciding where it should live from scratch.
I can return to older work without searching through a stack of disconnected drives.
I can change computers without treating the archive as something that belongs to the old one.
And I have recovery options when something goes wrong.
That is what I want from a creative system.
Not more process for the sake of process.
Not technology that constantly asks for attention.
The best archive is the one that recedes into the background — while the work remains organized, protected, and ready when I need it.