Call us — 01483 901310
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →
/ home / devices / server
Devices · servers

Server data recovery in Guildford.

Whatever state the server itself is in, recovery comes down to reaching the data on its drives. With the drives in hand, each is imaged read-only, any RAID array is rebuilt from the copies, and the file system — along with the files, virtual machines and databases sitting on it — is recovered.

From £500 · per server
Most jobs — no fix, no fee
RAID · VMware · Hyper-V
~ srv_2026-001 — live RECOVERED
$ bdr diagnose /dev/server
 Server: Dell PowerEdge · RAID 5 · 6 × 2 TB
 Status: ARRAY OFFLINE — 2 disks failed
 Client: confidential · Guildford GU2 8XH

$ bdr engineer-working
 Member disks: all 6 imaged read-only
 RAID 5: rebuilt off the controller
 Windows Server: volumes mounted

$ bdr verify
 ✓ file shares — 6.1 TB
 ✓ SQL databases — restored
 ✓ server recovered — data back
!

A failed server shouldn’t be left to rebuild its own array.

Server that won’t boot, a RAID array dropped offline, or a rebuild that stalled? Stop there — no rebuild, no re-initialise, no re-sync. Rebuilding lays down fresh writes and can smother the exact data we came for. Power the server down, note which bay each drive came out of, and call us. The drives almost always outlive the server, and that first recovery attempt is the safest one.

// faults we recover from

The server failures we take on.

The server work reaching us most runs from boxes that won’t boot to corrupt databases — hardware failures, RAID gone offline or degraded, rebuilds that failed, and virtual machines and databases turned corrupt.

Won’t boot or won’t POSTA server that won’t power on or POST usually points to the board, PSU or controller — yet the drives carrying your data stay perfectly fine. Get those drives to us and everything on them comes back.HardwareDeadRAID array dropped offlineOne failed disk too many, or a rebuild that went wrong, and the server’s RAID array drops offline. Each disk is imaged, the array reassembled from those copies, and the volumes recovered.RAIDOfflineWindows Server stuck or corruptWindows Server stuck in recovery, a boot volume gone corrupt, or an update that failed? The data is usually untouched — imaging the drives lets us bring back your files, roles and databases.OSBootRebuild that failed or dead controllerA RAID rebuild that fell over, or a controller (PERC, Smart Array) that has died? Rebuilds are where servers are lost most often — so we halt it, image the lot, and rebuild the array safely with the controller out of it.RebuildControllerESXi or Hyper-V host downA hypervisor host — ESXi or Hyper-V — that won’t boot, or a datastore gone corrupt with VMs that won’t start? We rebuild the underlying storage and bring back the VMs, VHDXs and VMDKs alike, with their data.VirtualVMsSQL, Exchange or database corruptAn Oracle, Exchange or SQL Server database gone corrupt, or a deleted mailbox store? The database files are recovered from the drives and repaired, bringing your data and mail back.DatabaseMailDeleted volume, VM or shareA server volume, a virtual machine or a shared folder deleted or formatted by accident? What lies beneath is usually still intact — imaging the drives lets us restore the deleted structure.LogicalDeletedPower loss or surgeA power cut or surge has dropped the server, or left its volumes corrupt. Salvaging what can be salvaged, we image every drive and take the array and file system back to their last consistent state.PowerSurgeBoot drive or single drive failedA boot drive that has died, or a lone non-RAID server drive — clicking, silent or undetected? On the clean-air bench we repair it, then image it to bring back the operating system and its data.DriveBoot
// servers we take on

Any server. Any role.

No server is out of scope — Dell, HPE, Lenovo, Supermicro, the rest — whether it runs Hyper-V, VMware, Linux or Windows Server. Whatever the make or the role, the data comes off the drives.

Dell PowerEdgeHPE ProLiantLenovo ThinkSystemSupermicroFujitsu PRIMERGYCisco UCSIBM System xIntelASUSGigabyteWindows ServerVMware ESXiHyper-VLinuxDell PERCHP Smart ArraySQL ServerExchangeActive DirectoryRAID 5SASNVMeReFSNTFS

Cisco UCS, Fujitsu PRIMERGY and Supermicro; Lenovo ThinkSystem; HPE ProLiant; Dell PowerEdge · blade, rack and tower · Hyper-V, VMware ESXi, Linux and Windows Server · HP Smart Array and Dell PERC RAID · Active Directory, Exchange and SQL Server · NVMe, SATA and SAS.

// how the recovery runs

How the recovery runs.

Send the drives in for a free diagnostic — with the server make, RAID setup and role — and an engineer scopes them, confirming the exact figure in writing before any work begins.

01

Free diagnostic

Tell us about the server — its make and model, the RAID setup, what it runs, what went wrong — and an engineer sizes it up and sends back a written quote, usually within 48 hours.

02

Image every drive

On dedicated hardware, every drive in the box — failing ones and all — gets a read-only image, so everything downstream runs on copies and your originals are never written to.

03

Repair failed drives

A drive that has failed — mechanically or on its electronics — goes onto the clean-air bench for new heads or a rebuilt board, just far enough to image and no more.

04

Rebuild the array

Where the server ran RAID, the array is worked out from the images — the disk order, the stripe size, the parity — and the volume rebuilt in software, no controller required.

05

Recover OS, VMs & databases

From the file system we pull everything on it — Active Directory, SQL and Exchange databases, virtual machines, files and shares — repairing databases and VMs wherever they need it.

06

Verify

Nothing is returned until the recovered volumes, databases and virtual machines have been opened and confirmed complete.

07

Return your data

Your recovered data comes back on new storage sized to the server, ready to restore and drop straight back into service.

// what we recover from

Any server. Recovered.

Post the drives or bring them in. Diagnosis first, quote next — and most jobs run no fix, no fee.

Every server
Dell, HPE, Lenovo +
Read-only
drives never altered
RAID & OS
rebuilt off the box
48 hr
Diagnostic turnaround
VMs & DBs
recovered
25 yrs
Recovering data
// get a custom quote

Request a written quote

Tell us what happened and we’ll get back to you, usually within a working day.

Prefer to call? 01483 901310 · Mon–Fri 9am–5:30pm

// pricing

Simple, tiered pricing.

Server recovery sits on a straightforward tier; you get a free diagnostic and see the quote in writing before any work starts.

Server recovery
From £500 + VAT
A single-drive or mirrored server starts at £500 + VAT; multi-disk RAID servers — RAID 5, 6 or 10 — open at £800. No fix, no fee covers most work.
  • Free diagnostic and a written quote up front
  • Single-drive or mirrored server from £500 + VAT
  • Multi-disk RAID server — RAID 5, 6, 10 — from £800 + VAT
  • Every drive imaged read-only, your originals left untouched
  • OS, VMs, databases and shares all recovered
// jobs off the bench

Recovered servers, real jobs.

A selection of recent server jobs — offline arrays, failed hosts, corrupt databases and deleted volumes. Identifying details stripped; every result verified.

// CASE 2026-038recovered
Dell PowerEdge · 6×2 TBRAID 5 · WindowsArray offline

Dell PowerEdge whose RAID 5 lost two disks.

Two of the array’s disks had gone. All six were imaged, the RAID 5 rebuilt, and the volume recovered.

// CASE 2026-032recovered
HPE ProLiant · 8×1.2 TBRAID 10 · Hyper-VWon't boot

HPE ProLiant Hyper-V host that wouldn’t boot.

A dead board, but the drives themselves were sound. We rebuilt the array off the drives and recovered the Hyper-V VMs.

// CASE 2026-026recovered
Dell PowerEdge · 2×1 TBRAID 1 · ExchangeDB corrupt

Exchange server carrying a corrupt mailbox store.

The RAID itself was fine; the Exchange database was the damage. We recovered the store and repaired it back to mounting.

// CASE 2026-019recovered
HPE ProLiant · 12×4 TBRAID 6 · ESXiFailed rebuild

VMware ESXi host whose RAID 6 rebuild went wrong.

The rebuild had written over part of the array. We imaged every disk, reconstructed the RAID 6, and lifted out the VMware datastore.

// CASE 2026-012recovered
Supermicro · 1×SSDLinux serverBoot drive dead

Linux web server whose boot SSD had died.

The SSD’s controller had failed. We recovered the NAND and rebuilt the Linux file system to bring the site and its data back.

// CASE 2026-005recovered
Dell PowerEdge · 4×3 TBRAID 5 · WindowsDeleted volume

Windows Server volume deleted mid-maintenance.

Hardly anything had landed on the data since. The array was rebuilt and the deleted volume recovered.

// getting it to us

Two easy steps.

Send the drives in for their free diagnostic with the server make, RAID setup and role; an engineer assesses it and confirms the exact quote in writing before any work starts.

1

Send us your device

Getting your data back starts with getting the drives — labelled in bay order — or the whole server to us. Pack it safely, enclose your contact details, and once we've run the free diagnostic we confirm your exact quote in writing before any work begins.

How to pack it
  • Pack the drives each wrapped anti-static and labelled with their bay order, in a sturdy carton with firm padding; or send the whole server, well protected.
  • You can leave out caddies, cables and power supplies — none of them are needed for the recovery.
  • Pop your details inside — name, address, phone and email, on a slip of paper or via our shipping form — and seal it up.
Post toGuildford Data Recovery
Building 2, Ground Floor, Guildford Business Park
Guildford GU2 8XH
Shipping formPDF · print & include with your devicePDF ↓

Posting it? A tracked, insured service is what we’d recommend. Rather drop it in? You’re welcome Monday to Friday, 9am to 5:30pm — just package the device up as above first.

2

Need more information?

Need a scoped quote first? Describe the server, RAID setup and fault on the form and an engineer will assess it and reply with a tailored quote.

An engineer reviews every enquiry personally — we usually reply within 30 minutes during the day. Prefer to call? 01483 901310.

Thanks — your message is in.

We’ll be in touch shortly. If it’s urgent, call 01483 901310.

// questions

Your server questions, answered.

The questions we’re asked most about recovering a server.

Usually, yes. A server that won’t boot most often has a hardware or OS fault rather than lost data. We image the drives, rebuild any RAID array, and recover the file system and everything on it from a copy.

Yes — it’s core server work. We image every member drive, work out the array geometry (disk order, stripe, parity) from the images, and rebuild the volume in software, recovering the data even from a degraded or failed-rebuild array.

Yes. With the array and file system rebuilt, the virtual machines (VMDK, VHDX) sit on the datastore like any other files — we extract them and, where one is corrupt, repair it back to booting.

Often, yes. With the volume recovered, we extract the SQL (MDF/LDF) or Exchange (EDB) database and, where it’s damaged, repair it to a consistent, mountable state ready to reattach.

It runs on tiers: a single-drive or mirrored server from £500 + VAT, and a multi-disk RAID server — RAID 5, 6 or 10 — from £800 + VAT. Each starts with a free diagnostic and a written quote.

You always get a free diagnostic and a written quote first. On multi-disk, mechanical and database work a deposit is taken against that quote, with the balance due only on a successful recovery.

All of them — Cisco UCS, Fujitsu PRIMERGY, Supermicro, Lenovo ThinkSystem, HPE ProLiant, Dell PowerEdge and custom builds; blade, rack and tower. Since we recover off the drives, the make and role rarely come into it.

You don’t. Most of the time you can pull just the drives and send them tagged with their bay order — that’s all we need. If it’s simpler, ship the whole server; either works.

Yes. A domain controller keeps AD in an ESE database (NTDS.dit) on the volume — with the file system recovered, we extract and, where needed, repair the AD database along with SYSVOL.

Most finish inside three to seven working days. The timing turns on the drive count, the RAID level, any database repair, and whether mechanical work is needed on the clean-air bench.

Pull the drives and label each with its bay order before sending, or ship the entire server — both are fine. Post it fully insured to the Guildford address, or drop it in on a weekday between 9am and 5:30pm.

// server failed?

Won’t boot, array offline or database corrupt? We’ll recover it.

Free to diagnose, priced on a tier from £500, and no fix no fee on the majority of jobs — every server recovered off the hardware, Dell, HPE, Windows Server, VMware and beyond. Get your recovery moving today.