Copy link to clipboard
Currently it's up to the user to check how many catalog backups have been created, and delete the oldest ones. For people with large catalogs, the amount of disk space consumed can be significant. It would be great if I could tell LR to create a maximum of 3 backups, and automatically replace the oldest one with the newest one.
currently, it's quite easy for people to unknowingly have a folder of Lr catalog backups that's 100+GB, as Lr merrily creates and adds new backups based on one's setting.
it would be great to have options to limit the folder size, to automatically delete backups older than a certain age, or to have a limit on the number of backups.
or, at least warn the user that the folder size is getting large
One can quickly eat into storage capacity if one neglects the deletion of old catalogue backups and 2nd copies of imported images. There is provision for automatic deletion of previews after a set time but not old catalogue backups nor imported 2nd copies. Catalogue backups are best deleted by number, that is to say, keep the most recent one, two or three and delete any older. Imported 2nd copies are really not needed after the images are processed so one could have a setting of automatic deletion after so many days. I wouldn't have thought this not difficult to implement.
Most of the people I know that have a Backup strategy use third party softwares (TimeMachine on MAC or SyncBack on PC) and don't use the LRC catalog Backup neither the 2nd copy because this is a endless storage usage and there is no process in LRC to manage the deletion. Me i use SynchBack that backup on a NAS and the NAS Backup on the cloud
I don't know if this plugin still works: https://www.photographers-toolbox.com/products/mdawson/tpglrbackup/
I use a utility on my Mac called 'Hazel' to do what you want.
Another thread here for the same Lightroom: Set Maximum # Of Catalog Backups, and Auto-Replace Oldest | Adobe Photoshop Family
A Backup Cleaner plugin for automatically removing old backups.
This thread is being merged into an existing authoritative thread for better tracking and response. Please review the official answer (if any) in the second post on the thread for more information.