A copy of an email that I have just sent to Support.
"Some observations on database/backup corruption issues when running on latest update to Mojave on iMac.
I have not had any problems with Luminar 3.0.2 losing images and edits until today when some of my photos went missing from the catalogue. I tried to reload Luminar and access backup but it kept crashing.
Yesterday I was exploring accessing Luminar from Lightroom via "Edit In" to take Lightroom development over into Luminar for stylising. Even if there is an instance of Luminar already running this process starts up another instance so that there are two copies of Luminar running using the same catalogue. Could having more than one copy of Luminar modifying the database lead to corruption in it and/or backups? On startup does Luminar do any cross checking between latest backup and catalogue database that might trigger an updating of the image gallery with incorrect data leading to photos being deleted from the database?
I renamed the backups folder in the Luminar catalogue and tried restarting Luminar again, this time it came up and photos had reappeared in the catalogue.
The original backups folder had a lot of recent entries which were just the backup files without the corresponding plist file. I deleted all the entries back until yesterday afternoon, renamed the backup folders so that the modified original was put back in place. After doing this Luminar loaded normally but some photos were still missing.
I did another reload of Luminar holding down option key to give list of backups and restored from a backup from early on yesterday. This restored the missing photos to the catalogue.
As an additional safeguard against future problems I took a manual backup of my catalogue and restored that as a test. While all the photos appeared one of my albums was empty, despite the original photos still being in their folders and accessible that way.
I repeated the backup/restore of the original catalogue and this time the album was correctly populated.
From these experiences it looks as though
- running multiple copies of Luminar at the same time may lead to database/backup corruption
- Edit-in from Lightroom will start a new copy of Luminar even if there is one running, so if using this best to ensure that no copies of Luminar are running when using Lightroom
- Can recover from some Luminar start-up crashes by deleting renaming the Backups folder within the Luminar catalogue folder, this may leave catalogue in usable state.
- Deleting recent entries from Backups folder may allow Luminar to be loaded with Option key held down allowing a restore from a backup prior to database corruption.
- Manual backup/restore process is not in itself reliable.
I am not sure that I can supply you with copies of catalogues etc as, even when they are compressed, they are large and my Internet upload speed is so slow that uploading would take an excessive time, but I am willing to try things out if that would help resolve the catalogue instability issues."
Please sign in to leave a comment.