Lightroom, library transfer to another harddrive

I recently have 'run out' of available space on my internal harddrive, on my desktop which runs WinXP and has Lightroom 2.0 on it. How do I retain the data which tells LR what adjustments to make to each .CR2 file, yet move the .CR2 data from the C: drive to the NAS?

Currently the LR catalog and the data files (.CR2) and output JPG files are all resident on the internal harddrive (.CR2 and .JPG both also backed up to an external USB harddrive). I just put in an order for a Network Available Storage (NAS) disk which will be connected via Ethernet thru a router. The intention is to put my LR data files on the NAS unit (and continue to back up .CR2 and .JPG to external USB drive), so that the internal harddrive has the LR software and maintains the catalog only, and no photo data is resident on the internal harddrive.

A bit of guidance about what I need to do, to accomplish this, would be appreciated.

Wilt--
i use a similar set up:
LR on internal hard drive, and all LR catalogues on the same drive.
All CR2/original image data on an external drive.
Occasionally i need to download images straight to the internal drive and then move them. its quite easy--I use LR1 still, but i imagine it same for LR2.

first you will need to create a directory structure within the external drive. Put a junk JPG into that folder. Then "Import" that folder. That will start up the directory tree within LR.

from there, you can create more folders within this folder on the external drive using LR: right-click on the folder within the folder pane, select "create folder as a child of this folder"
OR...with the "parent" folder selected, use the "+" button in the folder pane.

This will create the subfolders you need. Then, go to the folders within LR which contain the images you want to move, select them, then right-click the destination folder and choose "Move the Selceted Photo to this folder" This will actually move the originals on the disks, but it will keep all the LR data intact. BE SURE to expand all stacks! and turn off any filters! only the images highlighted will be moved.

full disclosure: i did experienced some weirdness when doing this the first time, for instance: LR did not want to create folders on the root of the external drive, thus the need for a "tree." I cant recall all the specifics, and you NAS may get you around some of these, but suffice it to say--do backup images, and try it with temporary copies of files, or within a new catalogue.

good luck! --alex.

Thanks for the information about bringing in new photos, Alex! You're right, it sounds quite easy!

Your closing paragraph abou the new catalogue...am I interpreting correctly that you suggest that as a trail run I create a new catalog, import a few pictures into that catalog and adjust them with LR, then use the technique which you wrote, as a trial move (before doing the actual transfer of 'real' data)?

yes, new catalog as a test of course. to get the tree structure as you want it you may need to go thru a few contortions, so its best to sort it out before spending time making the final version. cheers --alex.

Thanks. This reinforces the reason why I spend lots of time providing advice to others...I get great advice back in return!

What happens if you move some images or a whole folder that currently reside in a LR catalog when you open LR? Does LR inform you that some images are missing and does it give you a way to remap them? If so then can't you just move your current photo folder tree to the new drive and remap it?

BTW, why don't you keep the catalogs and your images on the same drive? Doesn't that make backing up easier?

There is another, possibly simpler, method one can use.

Step 1. Do an "Export as Catalogue" saving the export (eg FRED) on the NAS disk. This will create a folder FRED which will include the folder structure of your current catalogue, a previews folder (if selected on export) and fred.lrcat.

Step 2. Create a new catalogue in LR.

Step 3. Do an "Import From Catalogue" pointing to FRED.lrcat.

Step 4. do whatever with the files on the main machine

Edit. You can also use this method for only selected images of a catalogue.

gooble wrote in post #7170839
What happens if you move some images or a whole folder that currently reside in a LR catalog when you open LR? Does LR inform you that some images are missing and does it give you a way to remap them? If so then can't you just move your current photo folder tree to the new drive and remap it?

Yes, as far as I know. Lightroom places a "?" icon in the top right of the thumbnail, and when you click on it, it will ask for the new location. In addition, it will find all moved photos that were in the same folder as the original. The database is now updated to the new location. If you have all photos in one folder, you're golden. Otherwise it's a bit more work.

gooble wrote in post #7170839
BTW, why don't you keep the catalogs and your images on the same drive? Doesn't that make backing up easier?

You raise a good question, about any advantage or disadvantage to the LRCAT being out on a network drive rather than on a local harddrive!

I haven't experimented, but I'd bet the lrcat file on a network drive would seriously impact performance. That and the previews, plus the temporary journal files. They're all too active, so I'd make sure they were local.

JC4 wrote in post #7172075
I haven't experimented, but I'd bet the lrcat file on a network drive would seriously impact performance. That and the previews, plus the temporary journal files. They're all too active, so I'd make sure they were local.

You echo my own speculations about the catalog on a local drive. I'm still awaiting real confirmation, rather than both of us speculating the same!

JC4 wrote in post #7172075
I haven't experimented, but I'd bet the lrcat file on a network drive would seriously impact performance. That and the previews, plus the temporary journal files. They're all too active, so I'd make sure they were local.

Bingo!

My catalog file is 500mb (I've got everything from 2002 to the present in it at the moment). That and the previews across any network would be pushing it.

Wilt - do you export your LR edits to XMP, or store everything in the LR catalog?

If you've had your existing catalog for quite a while, and you routinely write edits to sidecars, you might also want to think about creating a new catalog and reimporting files in place from the server. My original catalog had been created way back in 1.0 and then converted each time an update/upgrade was released along the way. When I went to completely server based image storage, I decided to create a new catalog to ensure I was starting from a clean slate. I know that there had been some flaky things that had come up from time to time with my old catalog(s), and figured that was as good a time as any to clean things up.

Add in that many of my older files had been stored on external HDs (and backed up in other ways) and never added to a catalog, and it made it easier for me to start from scratch.

JC4 wrote in post #7172075
I haven't experimented, but I'd bet the lrcat file on a network drive would seriously impact performance.

Plus it won't let you, as the SQLite database isn't built for networks and there would be a risk of corruption if the network connection dropped at the wrong moment.

Victoria Bampton wrote in post #7172214
Plus it won't let you, as the SQLite database isn't built for networks and there would be a risk of corruption if the network connection dropped at the wrong moment.

...ergo, a moot question of performance! thanks. Can you comment about the 'optimal' setup for LR, assuming the typical desktop PC with internal and USB harddrives and NAS connected harddrives, taking into consideration not only data redundancy but also reasonable responsiveness in the system, and also for data migration as PCs are changed out? Would it be...

Local harddrive with LR software and catalog
[?USB or Network] for fast on-line access to active projects
[?USB or Network] for access to inactive projects
[?USB or Network] for data redundancy of all of the above