Data Recovery Case File · NAS & Network Storage · Two Jobs, One Device
The Same Box Was a Copy of Some Things and the Only Copy of Others
This enquiry describes an arrangement that is extremely common and quietly divided against itself. A four-drive network unit in long service, used "to back up my computer and store data", which has recently stopped responding. Those are two different jobs — and the contents are correspondingly split into material that exists in two places and material that exists only here, with nothing marking which is which.
| Media | Four-drive network storage unit in extended service — serving simultaneously as a backup destination and as primary storage; no longer responding |
| Reported situation | Four-drive network unit in service over an extended period · unit used as a backup destination for a computer · unit also used as primary storage for other material · unit connected by network and accessed wirelessly · unit no longer responding · contents required |
| Fault class | Undetermined pending member assessment — recovery scope determined by which contents exist elsewhere |
| Equipment used | Contents divided into duplicated and sole-copy material before any work · source machine verified for the backed-up portion · all members imaged individually write-blocked · array assembled offline · recovery prioritised to sole-copy material |
The decode: the split, and why nobody notices it
What a backup destination holds: a second copy of material that lives on a computer. If the unit fails, nothing is lost — the originals are still on the machine that was backed up, and the failure costs a reconfiguration rather than any data.
What primary storage holds: the only copy. Material moved onto the unit to free space, or written straight to it because it was the convenient large place — and for that material the unit is not a backup at all, whatever the rest of it is doing.
Why the two get mixed: because the device is one box with one name, and both kinds of use are sensible. A network unit is exactly the right place to send backups and exactly the right place to keep large files. Doing both is not a mistake — the mistake is losing track of which contents are which.
What that means at the moment of failure: the owner cannot say what has actually been lost. Half the anxiety is unnecessary and half is entirely justified, and until the split is worked out neither can be addressed.
So the first step costs nothing and reduces the case: establish what is on the source computer. Everything covered by the backup is safe there, and the recovery scope shrinks to whatever was only ever on the unit. That is frequently a much smaller job than the enquiry assumes.
Why sole-copy material should be prioritised in the capture: because if anything is difficult to read, effort belongs where losing it actually matters. Spending a fragile drive's remaining margin on files that exist on a laptop downstairs is the worst possible allocation, and it happens whenever a recovery proceeds without the split being known.
Why the array's health question is separate: a four-drive unit not responding may have a failed member, a failed enclosure, or a network fault — and the disks come out and are read regardless of which. The unit's own state does not determine the contents' state.
What to change afterwards, and it is one habit: keep the two roles apart. Send backups to the unit, and treat anything that lives only on it as requiring its own second copy elsewhere. A device cannot be a backup of itself.
On the bench
Contents were divided into duplicated and sole-copy material before any work — backed-up material existing on the source machine and costing nothing if the unit fails, while material written directly to the unit exists nowhere else regardless of the device's role. The source machine was verified for the backed-up portion, reducing scope. All members were imaged individually write-blocked, the array assembled offline, and recovery prioritised to sole-copy material.
The outcome
The contents divided before any work, the source machine verified and recovery prioritised to material existing nowhere else. 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: your unit was doing two jobs. Everything it backed up still exists on the computer it backed up. Everything written directly to it exists nowhere else — and nothing on the device marks which is which.
Network unit used for backups and for storage
Work out which of the two your missing material belongs to before commissioning anything — it will very likely shrink the job. Anything the unit backed up still exists on the computer it was backing up, so that portion costs you a reconfiguration rather than any data. Anything written directly to the unit, to free space or because it was the convenient large place, exists nowhere else, and for that material the device was never a backup at all. Doing both jobs on one box isn't a mistake; losing track of the split is. Afterwards, treat anything living only on the unit as needing its own second copy — a device can't be a backup of itself.
Check your computer first — then call Oxford Data Recovery on 01865 593000; contents divided before any work, every member imaged individually, recovery prioritised to material that exists nowhere else.
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.