142 Messages
•
3.7K Points
Fri, Apr 8, 2011 7:44 PM
27
Lightroom: Import Second Copy should be a true second copy
I would like the Import process to be able to create two copies of my imported original files, with matching filenames/formats and folder structures, on two separate disks. Then in the case of disk failure, I could just rename the backup disk to the name of the primary, or point Lightroom to the backup instead of the primary, and I'd be up and running again in no time.
I cannot use the Second Copy function at Import time because the second copy is not organized by date. I have to do this manually.
For me, the current Second Copy functionality is not useful in any way. I am requesting new functionality, where the second copy happens after renaming, DNG conversion, and organization into folders, so that the second copy is identical to the main copy in every way except the path to the parent folder.
I'm sure many will suggest that you need backup software anyway and so this shouldn't be Lightroom's job, but I disagree -- in my case, these date-organized folders of originals are truly read-only. I don't convert to DNG, I don't write out XMP sidecars, and in fact I don't delete originals after Import, so these folders are truly never written to again after Import. If I could just create a second copy at Import time, my backup system would never need to be involved and I could mark my disks or folders as read-only immediately after Import.
(It would be extra-cool if Lightroom would set the file and folder permissions to read-only itself!)
I cannot use the Second Copy function at Import time because the second copy is not organized by date. I have to do this manually.
For me, the current Second Copy functionality is not useful in any way. I am requesting new functionality, where the second copy happens after renaming, DNG conversion, and organization into folders, so that the second copy is identical to the main copy in every way except the path to the parent folder.
I'm sure many will suggest that you need backup software anyway and so this shouldn't be Lightroom's job, but I disagree -- in my case, these date-organized folders of originals are truly read-only. I don't convert to DNG, I don't write out XMP sidecars, and in fact I don't delete originals after Import, so these folders are truly never written to again after Import. If I could just create a second copy at Import time, my backup system would never need to be involved and I could mark my disks or folders as read-only immediately after Import.
(It would be extra-cool if Lightroom would set the file and folder permissions to read-only itself!)
Ideas
•
Updated
4 years ago
21
16
27
Helpful Widget
How can we improve?
Tags
import
lightroom
Responses
photographe
242 Messages
•
9.1K Points
10 years ago
0
rob_cole_2221866
4.5K Messages
•
76.3K Points
10 years ago
Personally, I would prefer a (Lr) scheme to simply restore photos from a backup. Then if that disk goes bad, just restore from the backup. That way, even if a person restructures or renames after importing, there is no problem.
As it stands, Lightroom supports making photo backups, but not restoring them, which seems to be the missing piece.
I would prefer to see Lightroom support backup and restoral completely - i.e. the ability to restore a catalog and/or presets and/or preferences, and/or photos... - no data left behind...
My motto: backup without restore is a job half done. And since Lightroom only supports backup of half the critical data, its more like a job 1/4 done.
Mark - I think you are in a minority with how you would want this. Another solution to your problem (wanting a mirror image of your photos so no copying to restore) would be just to do a folder-sync after import. Scooter Software's Beyond Compare would allow you to define a job to sync your photo folder tree with a secondary. Perhaps if Lightroom allowed Import Actions (to run post-Import, like they have now for post-Export), that would be all you need...
If I did not already have the ability to program any post-Import actions I may want (since I use 'RC Importer' plugin (which supports photo backup restoral)), I would request an Import Action feature, so I could run whatever kinda thing I wanted upon import...
5
0
photographe
242 Messages
•
9.1K Points
10 years ago
(Actually, to refine that slightly (i) one archive copy is RAW and two are DNG, (ii) I do push down xmp data to the primary DNG and back that up to the second DNG from time to time, but it's not crucial, (iii) I do backup TIFFs created by/for Photoshop. But the general idea still holds. I don't change file names or folder structure because LR does not handle that well. Files that I would want to delete are given 0 stars and put in a special collection so if I really want to delete them in the future I could, but I don't think I'd have an easy way of deleting the RAW versions of them. So I don't mind LR restoring files intelligently, but I see that as a huge understaking.)
1
0
a_tj
14 Messages
•
326 Points
10 years ago
I have no need for Lightroom to be my backup/restore process. I already have that in hand. I just simply want to be able to create a second copy of the imported files and place them where I want them.
1
bryn_forbes
165 Messages
•
3.2K Points
9 years ago
0
0
a_tj
14 Messages
•
326 Points
8 years ago
The reason I use and external HDD for my primary copy is the sheer volume of images. The second copy goes to the internal HDD as protection against drive failure. On a regular basis the images from the internal HDD are transferred to a Linux server and on a monthly basis they are backed up to DVD. All the images for one camera for one month are stored in the same folder - e.g. D300/201105 for images from the D300 in May 2011. At the end of May, all the images in 201105 will get backed up to DVD.
At the moment I use Nikon Transfer to transfer the images from memory card to HDD as it allows me to put the second copy where I want it and doesn't create an extra folder called "Imported on...". I would like to use Lightroom for the transfer and import but don't want the extra folder created. As can be seen from by backup workflow, I get no value from the "Imported on..." folder.
I would like to have an option to disable the creation of the "Imported on..." folder.
This reply was created from a merged topic originally titled
Lightroom: Allow prevention of creation of "Imported on..." folder when making a second copy on import.
0
0
photographe
242 Messages
•
9.1K Points
8 years ago
(2) Second Copy always creates an extra folder called "Imported on Saturday, April 16, 2011". This forces me to navigate to the folder in Windows Explorer to delete it. I would rather than have to do this.
(3) Creating the folder for the second copy is somewhat confusing. I often end up with a folder called "New Folder". Why not do it the same way as the First Copy (i.e. a Checkbox)
This reply was created from a merged topic originally titled
Lightroom: Import: Second Copy Folders difficult to create.
0
0
marcos_souza
13 Messages
•
316 Points
8 years ago
This reply was created from a merged topic originally titled
Liughtroom: Make additional copies during Import.
1
0
steve_365595
3 Messages
•
92 Points
8 years ago
I use this to automatically make a copy of each original image as it is imported. Having the second copy in a sub-folder means that I can't easily check which imports haven't been copied (for some reason LR often fails to make the second copy). I therefore move all of the files in the 'imported on november 6' folder into its parent, it is a bit boring after the tenth time, let alone the 30th, 40th etc.
Please apply all options set for the original folder to the second one, or tell me how to obtain a more permanent list of the copies that failed.
This reply was created from a merged topic originally titled
Lightroom: Apply import settings to second copy.
0
0
bryn_forbes
165 Messages
•
3.2K Points
8 years ago
Bryn Forbes 8 months ago
If the two drives matched in folder structure as the original poster asked, when backing up all I have to do is sync the catalog and the xmp files which is a very small amount of data (I have the option to write metadata in to jpeg, tiff and dng files turned off so the original files are unchanged and I can reverify this to make sure there are no corrupted files)
I know that this is just one way of working, but it's frustrating to me that the make 2nd copy is so close and could so easily make the same folder choices (subfoldername/2010-11-26 or whatever) as the original imported files, yet it doesn't.
0
0
bryn_forbes
165 Messages
•
3.2K Points
8 years ago
0
eric_burlet
68 Messages
•
1.4K Points
8 years ago
0
0
ptr727
1 Message
•
84 Points
5 years ago
LR CC can easily support this workflow by simply making a duplicate copy during import, same folder structure and same name as used for import, but a different destination folder.
0
0
geoff_long
2 Messages
•
80 Points
5 years ago
When importing, and choosing 'Make a Second Copy To', Lightroom names the file folders alphabetically, eg 'Imported on 14 December 2015' (using the non-American date format) so 14 December 2015 would come before 15 June 2015, for example.
If folders were named after the style 'Imported on 2015-12-14' they would be easier to find (and it be more logical).
0
0
andy_delgiudice
33 Messages
•
676 Points
4 years ago
It would be great to have more control over the redundant files created by the "Make a Second Copy" feature of the Import process.
I utilize a file renaming system upon import, and it would be useful to have the option to apply that same renaming process to second "backup" folder.
I realize that some users cull & purge before backing up, but I keep all images on redundant primary and backup drives so it would be great if Lightroom allowed for consistent naming across primary and secondary import locations.
0
0