P: Backup 'extended attributes' prevent backup software working

See also, my response to Assaf Frank which explains how this can be resolved per file, directory, or directory tree using Windows Powershell.

It's not an idea solution, but it will work. Depending on your backup software, it may take a bit for it to notice the file is no longer temporary or you may need to force it to rescan your files.

At least on Windows 10, the catalog backups created by Lightroom are left permanently marked as "temporary" in the filesystem:



PS D:\Amazon Drive\Lightroom Catalogs> Get-ChildItem . -recurse | where {$_.attributes -match "temporary"} | ft fullname,lastwritetime,attributes -autosize
FullName                                                                                             LastWriteTime                 Attributes
--------                                                                                             -------------                 ----------
D:\Amazon Drive\Lightroom Catalogs\2017-03-03 2258\Lightroom Catalog.lrcat.zip                     3/3/2017 10:59:05 PM  Archive, Temporary
D:\Amazon Drive\Lightroom Catalogs\2017-03-04 1358\Lightroom Catalog.lrcat.zip                     3/4/2017 1:58:23 PM   Archive, Temporary
D:\Amazon Drive\Lightroom Catalogs\2017-03-04 1618\Lightroom Catalog.lrcat.zip                     3/4/2017 4:19:09 PM   Archive, Temporary
D:\Amazon Drive\Lightroom Catalogs\2017-03-17 1942\Lightroom-Catalog.zip                             3/17/2017 7:42:43 PM  Archive, Temporary
D:\Amazon Drive\Lightroom Catalogs\2017-03-18 1042\Lightroom Catalog.lrcat.zip                     3/18/2017 10:43:10 AM Archive, Temporary

While I'm not aware of any issue this causes for Lightroom itself, it does cause Amazon Drive to deem the file temporary (because it is) and skip the sync that would otherwise occur:

[2017-03-18 10:52:49.387 -05:00  Info] [FileFilter] ignoring temporary file 


"D:\Amazon Drive\Lightroom Catalogs\2017-03-18 1042\Lightroom Catalog.lrcat.zip"

The behavior exhibited by Amazon Drive is definitely reasonable, and is not exclusive to it. I'm sure plenty of backup services will ignore temporary files since a file marked this way should be temporary.

When Lightroom finishes its backup, it really should remove the "temporary" filesystem attribute since the file really isn't temporary anymore.

Joseph, many thanks for the RoboCopy tip! It solves the issue for me. Have anyone tried to restore a zipped backup with the T attribute turned off? Maybe Adobe require to have it on for restore? (Which would be just as stupid as setting the temp attribute in the first place).

This is one of the reasons I switched to RoboCopy instead of Xcopy in my backup script. RoboCopy lets me turn off the "T" attribute.

This is really bad, and hard to understand that it cannot be fixed in over a year!!!

This is insane. Needs to be fixed!

Oh, the issue has been around longer than that. It would be such a simple thing to fix too!

Has this really been outstanding for a year when all sorts of cosmetic stuff has been coded into Lightroom?
EVERYONE who tries to backup their Lightroom backup zip files will find that they have not been in fact saved anywhere because of the erroneous Temp attribute set by Adobe on these critical files.

Yes, me too. I spent months tracking this down with my backup vendor.

I make regular backups of my Lightroom catalogue. I also like to have my catalogue backups included in my system backup. However, when Lightroom creates a backup of the catalogue, the zip file has the "temp" attribute set. Quite understandably, some backup software (including mine) will ignore files with the temp attribute set, so the catalogue backup is not backed up.
Thanks for reading,

Brian

The T attribute on Windows files is described by Microsoft as:

"The file is temporary. A temporary file contains data that is needed while an application is executing but is not needed after the application is finished. File systems try to keep all the data in memory for quicker access rather than flushing the data back to mass storage. A temporary file should be deleted by the application as soon as it is no longer needed."

It seems sensible therefore that backup software ignores these files, but I want my Lightroom backups backed up to my cloud storage.

I have worked around this for now by running a powershell script to remove this attribute as part of my backup process, but this should not be necessary.

This was not happening on earlier versions of Lightroom - the earlier files do not have this attribute set. It has taken several weeks in discussions with my backup software vendor to work out why my Lightroom backups were no longer being copied to my cloud storage.