Data Recovery Case File · Cameras, Drones & Cards · Redundancy Against the Wrong Thing
Two Cards Written Simultaneously Protect Against a Card, Not Against the Camera
Her enquiry comes from a professional who set things up correctly and lost work anyway. A wedding shot with dual-slot recording, around four hundred files missing, several recovery methods attempted — and her own assessment that "the camera is more at fault than the cards", the camera having since been replaced. She is very likely right, and it exposes the limit of the protection she was relying on.
| Media | Memory cards from a dual-slot camera recording simultaneously — approximately 400 files absent or unreadable; camera suspected as the origin and since replaced |
| Reported situation | Professional wedding coverage recorded to two card slots simultaneously · approximately 400 files missing or damaged · several consumer recovery methods attempted without result · camera suspected by the photographer as the origin of the fault · camera since replaced · content required for the client |
| Fault class | Write-side fault at the camera propagated to both cards — simultaneous recording reproducing the same defect on each; card media not necessarily implicated |
| Equipment used | Camera identified as a common-mode origin before either card was treated as faulty · both cards imaged write-blocked before any further scanning · both images compared to distinguish common defects from card-specific ones · file extents rebuilt from internal structure rather than estimated length · recovered files validated by opening at full resolution |
The decode: what dual-slot recording protects against, and what it does not
What the arrangement does: writes each frame to both cards as it is captured. Two complete copies accumulate in parallel, which is genuine protection and the reason professionals use it.
What it protects against: a card failing. If one card develops a fault, becomes corrupted or is lost, the other holds everything — and that is the failure it was designed for.
What it cannot protect against, and this is the point: a fault before the split. Both cards receive whatever the camera sends them, so a camera writing damaged data writes the same damaged data twice.
Why that makes the redundancy irrelevant here: the copies are faithful. Two identical copies of a corrupted file are two corrupted files, and comparing them yields nothing because they agree.
Why her diagnosis is well supported: two cards failing identically is far more likely to indicate a common cause than a coincidence. Independent card faults would produce different damage on each, and matching damage points upstream.
Why comparing the two images is nonetheless the first thing done: it separates the two possibilities directly. Where the cards differ, the difference is card-specific and one copy may be intact; where they agree, the fault came from the camera.
Why that comparison frequently recovers material: even a camera-side fault is rarely perfectly symmetrical. Timing differences between the two write paths mean the cards are not always damaged identically, and files complete on one and not the other are recoverable in full.
Why the consumer tools returned nothing: they look for whole valid files. A file written with damaged content is present and invalid rather than absent, so a scan reports nothing wrong and nothing recovered.
What is done instead: file extents are rebuilt from internal structure rather than from recorded lengths, and partial content reassembled where the stream permits. A file damaged in part is frequently usable in part, which matters a great deal for a wedding.
What the general lesson is, for anyone relying on dual slots: the second card protects the media and nothing before it. Verifying that files open — on a computer, not in the camera — is the check that catches a write-side fault, and it catches it on the day rather than afterwards.
On the bench
The camera was identified as a common-mode origin before either card was treated as faulty — dual-slot recording writing each frame to both cards in parallel and protecting against media failure, but not against a fault preceding the split, since both cards faithfully receive whatever the camera sends. Matching damage across two cards indicates a common cause rather than coincidence. Both images were compared to distinguish common defects from card-specific ones, timing differences frequently leaving files complete on one.
The outcome
The camera identified as a common-mode origin, both cards imaged and compared, and file extents rebuilt from internal structure. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: your redundancy was real and aimed at the wrong failure. Two cards protect against a card — both receive whatever the camera sends, so a camera writing damage writes it twice.
What dual-slot recording does and does not cover
Keep using it, and add one check: open a sample of files on a computer rather than reviewing them in the camera, before you leave. Writing to two cards protects you completely against a card failing, being corrupted or being lost — but both cards receive whatever the camera sends them, so a fault before the split is copied faithfully to each, and two identical copies of a damaged file are two damaged files. Reviewing in the camera won't catch it, because the camera reads embedded previews rather than decoding the full file.
Send both cards — call Manchester Data Recovery on 0161 871 0788; camera identified as a common-mode origin, both images compared for card-specific differences, extents rebuilt from internal structure.
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.