Originally Posted by
Colin Southern
I'm talking about undetected corruption of the LR Database, not XMP files. How on earth did they enter the conversation?
I'm not "hung up on the danger of losing an XMP file" in the slightest -- again, how did they enter the conversation? As a professional computer engineer who has seen tears in the eyes of grown men when they realised the cost of data that they've lost, I do however feel an obligation to point out the risks to people who don't have the benefit of the lessons a lifetime in the information technology industry has taught. And one of those lessons is "don't put all your eggs in one basket" ... which is EXACTLY what most folks are doing when they put all of their edits in a single LR database. And frankly, comments along the lines of "hey, it doesn't matter if you lose the lot because it's easy enough to redo them all" is just surreal -- I can't think of many who would want that daunting task. In fact, I can't think of any.
Most people using LR probably aren't backing up regularly at all - and those who do probably aren't retaining historical copies of the database (and thus not realising the consequence of over-writing all current backup sets with undetected corruptions in the database). And even if by chance they do discover an issue - and have historical backups available - they still have to jump through flaming hoops to export the relevant images from the relevant backup sets (being mindful not to lose work later than the backup). All for the sake of using DNG format and changing the default to store the edits with the files, not the database. No brainer in my opinion, but hey, I've only been looking after clients data for around 30 years.