Data Recovery Case File · Apple Mac · The Backup That Broke the Backup

Two patients, one mistake nobody warns you about: the shared Time Machine target decoded — and an iMac's history recovered from both of its failing sources

His enquiry laid out a two-front problem with the clarity of a man who'd already understood most of it. Front one: an old iMac that powers on, its internal drive clicking, the screen showing the flashing question-mark folder — "I suspect this is a physical failure, and I understand further attempts to access the drive could worsen the damage." Correct on both counts, and this archive's standing commendation applies. Front two, the one that earns this page: a Time Machine backup of that iMac, stored on his NAS — accessible and readable from his new Mac Mini — until he created a new Time Machine backup to the same NAS folder, after which the older backup bundle "can no longer be mounted." The safety net worked until a second net was thrown over it. What happened there is one of the least-documented traps in home Mac backup, and both fronts came home.

The decode: the question-mark folder, and why a second backup can break a first

Front one, briefly, because he'd read it right: the flashing question-mark is a Mac announcing it can find no bootable system — and paired with clicking from the drive, it's the mechanical genre this archive maps everywhere: the heads failing their work, each power-up another laboured attempt over the platters. His instinct to stop was the entire correct playbook. Front two, the trap, named properly: a Time Machine backup on a NAS lives as a bundle — a single intricate container holding the whole backup history as thousands of internal pieces, maintained by exacting bookkeeping that assumes one machine, one bundle, one orderly conversation with the share. Pointing a second machine's backup at the same target folder violates that assumption in exactly the ways bundles don't survive: contention on the share, interrupted housekeeping, and structural edits landing around a container mid-thought — after which the older bundle's bookkeeping no longer adds up and mounting fails. The cruelty of the failure is its timing and its innocence: the action that breaks the old backup is making a new backup, performed at precisely the moment backups matter most, and no dialog warns against it. The doctrine, filed for every household with a NAS: one backup target per machine — separate folders at minimum, separate shares ideally — and an old machine's final backup gets copied aside as a read-only archive before its successor ever starts backing up. The mercy in his version: an unmountable bundle is a container with damaged bookkeeping, not erased contents — the history inside remains substantially present, waiting for structural repair rather than mourning.

The recovery — both fronts, then the merge

The iMac's drive took the mechanical road: opened at the laminar flow bench, its spent heads replaced with a matched donor stack, and imaged on the PC-3000 at post-failure tempo — coverage closing in the high ninety-nines, the volume mounting whole from the image with his estate current to the iMac's last day. The bundle took the structural road in parallel: its damaged bookkeeping repaired at container level until the backup history mounted again, yielding the archive's depth — versions and files reaching back through the iMac's years. Then the step a two-source case earns: the recoveries merged and cross-verified, the drive's current-day estate reconciled against the bundle's history, gaps in either covered by the other, duplicates resolved, and the whole delivered organised on new media in duplicate. The report ratified his two suspicions in print — physical failure, correctly left alone; bundle damaged by the shared target, not by anything the data did — and closed with the NAS's new arrangement already configured: one machine, one folder, and the old iMac's history parked read-only where no future backup can reach it.

Outcome

Both sources recovered, merged, and verified — and two filings for every Mac household running backups to a box in the cupboard. On the drive: clicking plus the question-mark folder is a stop instruction, and his obedience to it preserved a near-complete image; the commendation stands. On the backup: never point two machines at one Time Machine target — the new backup is the one thing that can break the old one, silently, at the worst possible moment; give each machine its own folder, and archive a retired machine's final bundle read-only before its successor's first run. An unmountable bundle is repairable; an overwritten arrangement is a lesson. He brought both patients in untouched and correctly diagnosed, and got both histories back — which is what asking first, on both fronts, reliably buys.

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.