Skip to main content
Known Participant
May 1, 2011 9:55 PM UTC
Open for Voting

P: Allow Catalog to be stored on a networked drive.

I'd love to make LR more multi-computer friendly. I have no doubt that there's probably database architecture issues and a host of other barriers... But I have to believe that the need for either multi-user or at at lease multi-computer use is widely desired. And yes, I know you can do the catalog import export thing but I find this less than ideal.

570 replies

Participant
Sep 2, 2026 1:33 PM UTC

The option to save the catalogue on a network drive (NAS) would be very helpful, as this would allow for automatic data backups.


Storing data on a physical drive always carries the risk of data loss. When the computers are reset to their factory settings overnight, this results in the local catalogues being deleted. Due to increased security requirements, no data should be stored on local drives. This approach is simply no longer appropriate.
 

Translate
RRKing
Inspiring
Sep 18, 2024 10:50 AM UTC

It's a little late but the only way to "properly" host your catalog and images and everything on a NAS is to use LUNs and attach them via iSCSI.  I've been doing this for years with zero issues and i have had network fails and power outages and all kinds of madness over the last 9 years and never had a problem with corruption and even if i did i ahve proper backups becuase it's on my NAS.

One thing i will say is my NAS is attached via a fiber 10gig conenction (or it was now i use 25gig) and so i never have speed issues and 100% of my LR data is over the network.  Keep in mind iSCSI is basically a local drive that is connected over a network so thats why LR works off of it.  

Translate
Inspiring
Sep 10, 2024 2:46 AM UTC

@jrellis: A question: LR uses WAL (Write Ahead Logging) journaling mode for the SQLite catalog database. But the SQLite documentation says "WAL does not work over a network filesystem". That page says that when an app requests WAL via:

PRAGMA journal_mode=WAL;

the journaling mode will remain the default mode (rollback) if the filesystem containing the database doesn't support WAL.

So it seems your LR is running in the older and somewhat slower rollback journaling mode.  I wouldn't hazard any guesses whether that makes a differnce to LR performance in practice.

 

The full quote from the SQLite documentation is:

 

1.  All processes using a database must be on the same host computer; WAL does not work over a network filesystem. This is because WAL requires all processes to share a small amount of memory and processes on separate host machines obviously cannot share memory with each other.

 

This restriction doesn't apply when all processes using a database do reside on the same host computer, which is the situation with LrC.  LrC locks the catalog with both the SQLite database lock and by creating a file in the catalog directory, preventing another instance of LrC from accessing the catalog from another PC.

 

I am running the latest LrC (13.5.1) and it is using WAL.

Translate
johnrellis
Legend
Sep 10, 2024 2:02 AM UTC

@keg415, thanks for the clear write-up -- that could be useful to many others. 

 

So making a Windows junction to a symbolic link to the remote directory containing the catalog fools LR into thinking that directory is not on a network volume.

 

A question: LR uses WAL (Write Ahead Logging) journaling mode for the SQLite catalog database. But the SQLite documentation says "WAL does not work over a network filesystem". That page says that when an app requests WAL via:

 

PRAGMA journal_mode=WAL;

the journaling mode will remain the default mode (rollback) if the filesystem containing the database doesn't support WAL.

 

So it seems your LR is running in the older and somewhat slower rollback journaling mode.  I wouldn't hazard any guesses whether that makes a differnce to LR performance in practice.

 

 

Translate
Inspiring
Sep 9, 2024 6:39 PM UTC

Allow a catalog to be stored on a network drive.  This is a much-requested feature that is simple to implement -- the check to prevent it just needs to be removed.  I've stored catalogs on a NAS for over a decade without experiencing corruption.  I've researched this thorougly, please see the attachement for details and references.

 

A related feature, for which I'm submitting a separate request, is to allow the location of the previews cache to be changed so that it can be stored separately from the catalog.  This would allow the previews to be stored on an SSD to improve performance when the catalog is on a network drive.

Translate
KostFan2
Known Participant
Feb 4, 2024 7:54 AM UTC

I have been using this method and it works well

Translate
Participant
Feb 3, 2024 2:30 PM UTC

Feature Request for a possibility to use Adobe Lightroom Classic on different computers across a local network, with implementing a similar solution as DaVinci Resolve Project Server.

 

With DaVinci Resolve you can choose if you have projects saved locally on a computer, or you connect to the Project Server running on a main computer to open a project from there. The Project Server take care of making sure that two computers are not working on the same project at the same time.

 

Can this be possible?

Translate
Sean McCormack
Community Expert
Community Expert
Feb 3, 2024 3:08 PM UTC

Two issues. One is that the constant writing that's happening with the catalog gets corrupted on a network. The second is database is SQLite which is single user. You'd need a complete rewrite of the database which would probably require a licensed multiuser database increasing the cost of Lightroom. 

Translate
Sean McCormack. Author of 'Essential Development 3'. Magazine Writer. Former Official Fuji X-Photographer.
Inspiring
May 16, 2023 4:16 PM UTC

Yes, but at least it's clear that storing the catalog on a network drive isn't causing this problem.

Translate
johnrellis
Legend
May 15, 2023 10:50 PM UTC

So ambiguous results above where the problem might be...

Translate
Inspiring
May 15, 2023 10:06 PM UTC

I tested with the suggested settings ("Replace Embedded Previews With Standard Previews During Idle Time" and "Generate Previews In Parallel" were already disabled) and found that Import/Add worked, but Synchronize Folder failed (twice). I then retested Import/Add with normal start options, Build Previews:1:1 and everything on the NAS, and that also worked, though I'm fairly sure Import/Add with this configuration has also failed at least once. I don't recall Synchronize Folder ever succeeding with a large number of photos. I'm surprised there's much difference between Import/Add and Synchronize Folder.

Translate