Nov 222009
 

Backup-1.jpgYou know that sinking feeling you get when you go to open a file and it’s not there or the entire hard drive just won’t mount? Your mind races. You wonder where you put that backup. Wait! Did you back that up?

It is usually an event like this that finally makes all those articles about backing up make so much sense. Well, if you haven’t paid heed thus far perhaps this article will finally give you that extra push. At least as far as Lightroom is concerned. That’s it. Start small and build up to full backups!

Before we look at what Lightroom provides for backing up we should touch on the general need for backing up your data overall. The American Society of Media Photographers (ASMP), with funding from the Library of Congress, has put together an amazing site that every digital photographer should visit regularly, dpBestFlow.org. For our purposes you should take a look at the backup sections for a complete discussion of backup philosophy. Develop the mindset that no file exists until it exists in three places (and one of those needs to be offsite!).

Now, back to Lightroom. There are two separate backup issues when dealing with Lightroom; the catalog and the original source image files. Lightroom let’s you make a backup copy of your image files while you import them.

Import Photos.png

Choose a backup location in the Import dialog and Lightroom will make a second copy of the files there. I suggest that this location be on a different drive from where you are storing the files used in the catalog.

One issue with this is that Lightroom makes a copy of the files using their original names. So if you are renaming them during import it may be challenging to match them up later should you need to recover a file. Lightroom 3 Note: This has been addressed in Lightroom 3 Beta. Files you choose to backup during import will be backed up using the same renaming conventions you choose for the imported files.

Even with this provision I recommend you regularly make a backup of your source image files as they are saved on the hard drive.

The Lightroom catalog is another file that needs to be backed up. This is the file with the extension .lrcat and is the database that houses all the information about your images and the work you have done. Lightroom lets you choose a regular backup routine for this file in the catalog settings.

Catalog Settings.png

Your choices here are:

  • Never
  • Once a month
  • Once a week
  • Once a day
  • Every time Lightroom opens
  • the Next time Lightroom opens

What you choose depends on how much security you want. I generally choose to backup every time I open the catalog. Choose the option that best fits your workflow. However, I strongly caution against choosing Never.

So where is the backup? You get to choose that when the backup dialog appears upon opening the catalog.

Back Up Catalog.png

Again, choose a location on a different drive than your working catalog.

Lightroom 3 Note: This seemingly backward approach of backing up BEFORE you work on your images has been addressed in Lightroom 3 Beta. Now you are asked to backup when closing the catalog (i.e. – AFTER you have worked in the catalog.

So take advantage of the backup resources Lightroom provides. Take a look at the dpBestFlow.org site and adopt an overall backup discipline. Never have that sinking feeling again when a file goes missing!

No related posts.

Line Break

About the Author:
Contact Gene


Gene is an Adobe Community Professional and and Adobe Certified Expert in Photoshop Lightroom, Photoshop, and InDesign, and an avid Lightroom fan. He belongs to the Professional Photographers of America (PPA) and the National Association of Photoshop Professionals (NAPP). Gene also the Co-Founder, Manager and a frequent blogger for the Dallas Fort Worth Adobe User Group (DFWAUG).

In addition to running Lightroom Secrets, Gene also contributes to O'Reilly's media blog, moderates on the Adobe forums, and helps out on lightroomforums.net.

  • Pingback: Tweets that mention You Do Have a Backup…Don’t You? -- Topsy.com

  • Pingback: Twitted by LRSecrets

  • http://twitter.com/davecornwell David Cornwell

    Backing up photos

  • gunnarr

    And with no way to restore from your image backup in Lightroom, you have to seek tru the whole backup for each image that you have lost…
    After a harddisk crash I lost some hundred images. I had a backup of them, but I had to manualy look up one and one image from the backup manualy to restor lost files in the database. A very time-consuming work.

    Or is there any other way to do it?

  • http://lightroomsecrets.com Gene McCullagh

    Hi gunnarr!

    First of all, you can never have too many backups. There are two distinct things that need to be backed up in LR; (1) the catalog and (2) the source image files. Restoring the catalog is easy and well implemented in LR. However, restoring the source image files is not.

    Yes, LR does provide an easy mechanism to make backups of those files during an import but it doesn't keep track of them after that. Nor does it apply any new names to the backup files if you are renaming files on import. LR 3 Beta addresses this issue by applying any renames to the backup files as well. That solves the problem of trying to match up _IMG02154.CR2 with Jack-Birthday-2007-02.CR2.

    The backup pool created by LR is just one leg of a good backup strategy. It's a place where you can easily grab a couple of lost or corrupted files. It isn't a great place to go if you have a major disk failure and lose everything. That's where the second leg comes in.

    As a general practice, you should be backing up your drive separate and apart from LR. That way when you lose a disk you can restore all the contents AND THE FOLDER STRUCTURE from the backup. If your folder structure is put back intact then LR will see everything where it should be and you can go on with your work.

    On a Mac you can use a utility like Super Duper or Carbon Copy Cloner to make exact (and bootable) copies of your drive. Another option is something like Carbonite or Mosey for “in the cloud” backups (which is the third leg of this backup stool – offsite storage). Perhaps Windows readers can offer some suggestions on that OS for this.

  • gunnarr

    And with no way to restore from your image backup in Lightroom, you have to seek tru the whole backup for each image that you have lost…
    After a harddisk crash I lost some hundred images. I had a backup of them, but I had to manualy look up one and one image from the backup manualy to restor lost files in the database. A very time-consuming work.

    Or is there any other way to do it?

  • http://lightroomsecrets.com Gene McCullagh

    Hi gunnarr!

    First of all, you can never have too many backups. There are two distinct things that need to be backed up in LR; (1) the catalog and (2) the source image files. Restoring the catalog is easy and well implemented in LR. However, restoring the source image files is not.

    Yes, LR does provide an easy mechanism to make backups of those files during an import but it doesn’t keep track of them after that. Nor does it apply any new names to the backup files if you are renaming files on import. LR 3 Beta addresses this issue by applying any renames to the backup files as well. That solves the problem of trying to match up _IMG02154.CR2 with Jack-Birthday-2007-02.CR2.

    The backup pool created by LR is just one leg of a good backup strategy. It’s a place where you can easily grab a couple of lost or corrupted files. It isn’t a great place to go if you have a major disk failure and lose everything. That’s where the second leg comes in.

    As a general practice, you should be backing up your drive separate and apart from LR. That way when you lose a disk you can restore all the contents AND THE FOLDER STRUCTURE from the backup. If your folder structure is put back intact then LR will see everything where it should be and you can go on with your work.

    On a Mac you can use a utility like Super Duper or Carbon Copy Cloner to make exact (and bootable) copies of your drive. Another option is something like Carbonite or Mosey for “in the cloud” backups (which is the third leg of this backup stool – offsite storage). Perhaps Windows readers can offer some suggestions on that OS for this.