Data Recovery Case File · Formatted & Logical Faults · Scope It by the Gap
A Backup With Conditions Has a Shape
His enquiry is unusually well organised and contains its own scoping. A laptop "that is not powering up — completely dead, not even trying to boot up. I have back-ups of almost everything because this is done automatically when it is powered up and connected to the internet, however" — and the qualification is where the work is. A backup that runs under conditions has a gap shaped exactly like those conditions, and describing it converts a vague worry into a short, specific list.
| Media | Laptop internal drive from a machine with no power response — automatic backup in place, conditional on the machine being powered and connected |
| Reported situation | Machine entirely without power response · no boot attempt · automatic backup configured, running when the machine is powered and connected to a network · most content believed backed up · a gap remaining since the last successful backup |
| Fault class | Host power failure with storage unaffected — recovery scope defined by the interval since the last successful backup |
| Equipment used | Last successful backup date established before assessment · drive removed and read independently of the machine · imaged write-blocked · recovery scoped to material created or modified since the backup date · results reconciled against the backup set |
The decode: why the machine is irrelevant, and how to define the gap
Why a completely dead machine is not a storage problem: no power response means a power path fault — the adapter, the charging circuitry, the board's power management, or a component failure. None of those involve the drive. A machine that will not power on tells you nothing whatever about its storage, and the drive comes out and reads on any other computer. That is the whole of the technical position.
Why his backup arrangement is the more interesting part: it runs when the machine is powered and connected. That means it captures nothing while the machine is off, nothing while it is offline, and nothing created after the last time both conditions were met. So the exposure is not "some things might be missing" — it is precisely everything created or modified between the last successful backup and the moment the machine died.
How to establish that date, and it costs nothing: the backup service records when it last completed. Signing in through its web interface shows the date, and frequently a file list. That single figure defines the entire recovery — everything before it is safe, everything after it is what needs retrieving, and the job is scoped to a window rather than a whole drive.
Why that makes this cheaper and faster: a recovery scoped to files modified after a known date can be targeted, confirmed and delivered quickly, rather than reconstructing an entire filesystem and handing back material the owner already has in duplicate. Very few people can define their gap this precisely, and it is worth doing before commissioning anything.
The failure mode worth checking while he is there: that the backup was genuinely completing rather than merely running. Services report a last successful backup separately from a last attempt, and a machine that had been offline or had a full quota may show attempts continuing while nothing actually landed. The date to trust is the last success, and it is sometimes considerably older than people expect.
What to check about the machine itself, separately: whether it is a simple power fault — a failed adapter or charging circuit — since that is often an inexpensive repair, and a machine returned to life makes the recovery unnecessary. Establishing that before commissioning data work is worth an afternoon.
On the bench
The last successful backup date was established before assessment — a conditional backup capturing nothing while the machine was off or offline, so that single date defines the entire exposure and scopes the work to a window rather than a drive. The distinction between last attempt and last success was confirmed. The drive was removed and read independently of the machine, imaged write-blocked, recovery scoped to material created or modified since that date, and results reconciled against the existing backup set.
The outcome
The backup date established first, the drive read independently and recovery scoped to the gap and reconciled against the existing set. 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: a machine that will not power on says nothing about its storage, so the drive reads elsewhere. And a backup with conditions has a gap shaped like those conditions — find the last successful backup date, which services report separately from the last attempt, and that figure defines exactly what needs recovering.
Dead machine with an automatic backup you mostly trust
Sign in to your backup service through its website and find the date of the last successful backup — that one figure defines your entire problem. Services report the last attempt separately from the last completion, and a machine that had been offline or hit a quota can show attempts continuing while nothing actually landed, so the success date is sometimes considerably older than expected. Everything before it is safe and everything after it is what needs retrieving, which scopes a recovery to a window rather than a whole drive and makes it faster and cheaper. Meanwhile, a machine with no power response tells you nothing about its storage — that's a power fault, the drive is fine, and it reads on any other computer.
Find your last successful backup date — then call Guildford Data Recovery on 01483 901310; drive read independently of the machine, recovery scoped to the gap and reconciled against your existing set.
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.