Data Recovery Case File · Mac & Apple Ecosystem · Recover the Package, Not the Pictures
The Catalogue Is Part of the Data
His enquiry names what is on the drive, and the naming matters more than usual. A desktop machine from 2012 that will not start: "it still has a lot of photos on — the drive is almost full — along with editing catalogue data that hasn't been backed up externally. I'd like to get that back and transfer it to a" new machine. Two words in that sentence change how the job should be done. A photo library and an editing catalogue are not folders of images — they are structured objects, and recovering the pictures out of them is not the same as recovering them.
| Media | All-in-one desktop internal hard drive, 2012 generation with removable storage — machine not starting; photo library and editing catalogue held, drive close to capacity |
| Reported situation | Machine failing to start · manufacturer support unable to assist · photo library and editing catalogue held on the internal drive · no external backup of the catalogue data · drive close to full · transfer to a new machine intended |
| Fault class | Machine failure with removable storage — library and catalogue structures requiring recovery as complete objects rather than as constituent files |
| Equipment used | Storage removed and read on a generation-matched adapter · imaged write-blocked independently of the machine · library packages and catalogue structures recovered as whole objects · internal databases validated by opening in their applications |
The decode: what a library actually is, and why it must stay whole
What a photo library contains: not a folder of pictures. It is a package — a directory the system presents as a single item, holding the original image files, generated previews at several sizes, and a database recording albums, dates, faces, edits, keywords and every adjustment ever made. The photographs are in there, but so is everything that makes them a library rather than a pile.
What an editing catalogue is: the same idea taken further. The catalogue is a database describing where each image lives and what has been done to it — crops, exposure, colour work, virtual copies, collections and history. The edits are not in the image files. They exist only in the catalogue, which is why a catalogue lost is years of work lost even when every original photograph survives.
Why that changes the recovery: a job scoped to "recover the photographs" can succeed completely and deliver a folder of original images with every adjustment gone, every album dissolved and every date grouping lost. Technically that is thousands of files recovered. Practically it is a library reduced to its raw contents. The deliverable has to be the package and the catalogue as whole objects, with their internal structure intact, so that they open in their applications and behave as they did.
Why that has to be said up front: because a recovery optimising for the largest number of recovered files will happily carve individual images out of a package and count them as successes. Naming the library and the catalogue as the deliverable, and asking for them to be validated by opening in the application rather than by file count, is what makes the difference.
Why the machine's condition is largely irrelevant: a desktop of that generation carries an ordinary internal drive that comes out and reads on a standard adapter. The machine failing to start does not bear on the storage, and the manufacturer being unable to help concerns the computer rather than the data.
Why "the drive is almost full" is worth knowing: a nearly full drive has little free space, which means comparatively little room for anything to have been overwritten — but it also means the material is spread across the whole surface rather than concentrated near the start, so imaging cannot be scoped to a small region. It is a fact worth reporting either way.
The point for anyone with a catalogue: back up the catalogue file itself, separately and often. It is small, it is the irreplaceable part, and almost nobody does.
On the bench
The storage was removed and read on a generation-matched adapter, the machine's failure to start having no bearing on a drive that lifts out. It was imaged write-blocked independently of the machine. Library packages and catalogue structures were recovered as whole objects rather than as constituent files — since a package carved into its individual images returns photographs without albums, dates or adjustments, all of which live in the internal database. Catalogues were validated by opening in their applications rather than by file count.
The outcome
The storage read independently of the machine and the library and catalogue recovered whole and validated by opening. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone with a photo library or editing catalogue: those are packages containing a database as well as images, and your edits, albums, keywords and dates live in the database rather than in the picture files. So a recovery that returns every photograph can still lose years of work. Ask for the library and catalogue as whole objects, validated by opening in the application.
Recovering a photo library or editing catalogue
Say that's what it is, and ask for it back as a whole object rather than as photographs. A photo library isn't a folder of pictures — it's a package holding the originals, generated previews, and a database recording albums, dates, keywords and every adjustment you've made. An editing catalogue is the same idea: your crops, exposure work and colour adjustments exist only in that database, not in the image files. So a recovery can return every single photograph and still lose years of work, because what came back is the raw contents rather than the library. Ask for it validated by opening in the application, not by file count. And once you're set up again, back up the catalogue file separately — it's small and it's the irreplaceable part.
Ask for the package whole — call Newcastle Data Recovery on 0191 406 1051; storage read on a matched adapter, libraries recovered as complete objects, catalogues validated by opening in their applications.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.