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

SAN storage recovery in Guildford.

An offline storage pool, controllers that have died, a LUN that vanished, or a datastore gone corrupt — on enterprise SANs from Dell EMC, HPE, NetApp, IBM and beyond, over iSCSI or Fibre Channel, we get the volumes back. The volumes are rebuilt from the disks up: every disk in the affected pool imaged, the RAID groups, storage pool and LUN layout reconstructed, and the file system rebuilt on top of it.

Quoted per array
Most jobs — no fix, no fee
Fibre Channel · iSCSI
~ san_2026-001 — live RECOVERED
$ bdr diagnose /dev/san
 Array: Dell EMC Unity · 24 × 1.8 TB · RAID 5
 Status: POOL OFFLINE — 2 disks failed in pool
 Client: confidential · Guildford GU2 8XH

$ bdr engineer-working
 Member disks: all 24 imaged read-only
 Storage pool: rebuilt off the array
 LUNs: remapped · volumes back

$ bdr verify
 ✓ datastores — 31 TB
 ✓ VMs — restored
 ✓ SAN recovered — data back
!

A failed SAN should not be left to rebuild or re-initialise its pool.

Pool dropped offline, a controller lost, a rebuild that has stalled? Stop — no rebuild, no re-initialise, no re-sync should run. Each of those lays down fresh writes and can smother the data we need, and spinning up a fresh pool or LUN can wipe the very map that finds it. Kill the power, note which shelf and slot each disk came out of, and call us. That opening attempt is the safest there is, so it should be ours.

// faults we recover from

The SAN failures we take on.

The SAN work reaching us most runs from offline pools and corrupt datastores to dead controllers, LUNs deleted or reformatted, rebuilds and expansions that failed, and VMFS datastores gone bad.

Pool or RAID group gone offlineWhen a pool or RAID group loses more disks than it can carry, its LUNs drop offline. We image every disk and reassemble the pool from the copies to return the volumes.PoolOfflineLUN deleted, unmapped or reformattedA LUN wiped, unmapped, trespassed or reformatted by accident? The blocks beneath it are usually still present — we rebuild the LUN out of the pool and recover what it held.LUNDeletedStorage processor or controller downA failed storage processor or controller can leave the SAN refusing to present its volumes even after failover. We lift the configuration, image the disks and rebuild the LUNs clear of the hardware.ControllerSPRebuild or expansion that failedA disk rebuild or a pool expansion that stalled or corrupted the array. Rebuilds and migrations are where SANs are lost most often — so we halt it, image the lot, and reconstruct from safety.RebuildHigh riskVMFS datastore or VM won’t startA VMware datastore on a SAN LUN turned corrupt, or virtual machines that refuse to power on? We rebuild the LUN, mend the VMFS, and recover the VMDKs along with their data.VMFSVMsPool metadata or thin-provisioning damageThe tables that pinpoint your data — pool metadata, the thin-provisioning map — can corrupt after a bad disk or a power cut. We rebuild that mapping and piece the LUNs back together.MetadataThinFirmware or array-OS update gone wrongA firmware or array-OS update that bricked the controllers or lost the configuration? The disks still hold your data — we read it off them and put the LUNs back together with the box left out entirely.FirmwareUpdatePower loss or write-cache corruptionOne data-centre outage can drop shelves and controllers together, and any write cache not yet flushed corrupts the LUNs as it goes. Every disk gets imaged, and the volumes are rebuilt to their last consistent state.PowerCacheDisks or shelves in the wrong orderDisks shuffled between slots, or a shelf pulled during a fault? We work out where each disk belongs in the pool and rebuild the array from the correct arrangement.OrderShelves
// SANs we take on

Any array. Any LUN.

No SAN is out of scope — Dell EMC, HPE, NetApp, IBM, the rest — over iSCSI or Fibre Channel, at any RAID level and pool layout. Whatever the platform, the volumes are rebuilt from the disks themselves.

Dell EMCHPENetAppIBMHitachiPure StorageFujitsuLenovoInfortrendPromiseHuaweiDataCoreFibre ChanneliSCSILUNVMFSStorage PoolRAID 5RAID 6RAID 10Thin ProvisionDedupDual ControllerSnapshot

Hitachi VSP and Pure Storage; IBM FlashSystem and Storwize; NetApp E-Series, AFF and FAS; HPE MSA, Nimble and 3PAR; Dell EMC Compellent, PowerStore, Unity and VNX · iSCSI and Fibre Channel · storage pools with RAID 5, 6 and 10 · clustered volumes plus VMFS, NTFS and ReFS · arrays single- and multi-shelf.

// how the recovery runs

How the recovery runs.

Send the disks from the affected pool in for a free diagnostic — with the array make, model and RAID layout — and an engineer scopes them, putting the exact per-array figure in writing before any work begins.

01

Free diagnostic

Tell us about the array — its make and model, the RAID layout, how many disks, what failed — and an engineer sizes it up and sends back a written quote, usually within 48 hours.

02

Image every disk

Working on dedicated hardware, we take a read-only image of each disk from the affected pool, failing ones and all, so everything downstream runs on copies and your originals stay untouched.

03

Repair failed disks

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

04

Rebuild the pool & LUNs

Off the images, the RAID groups or storage pool go back together, along with the thin-provisioning map and the layout of each LUN — every extent returned to where it belongs.

05

Recover the file system

On top of the LUN we rebuild the file system — ReFS, NTFS or VMFS — and pull out your virtual machines, databases and files, repairing VMs and databases wherever they need it.

06

Verify

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

07

Return your data

Your recovered data comes back on new storage scaled to the volumes, set to go straight back into service.

// what we recover from

Any SAN. Recovered.

Post the disks or bring them in. Diagnosis first, the per-array quote next — and most jobs are no fix, no fee.

Every SAN
Dell EMC, HPE +
Read-only
disks never altered
Off the array
LUNs rebuilt
48 hr
Diagnostic turnaround
VMware
VMs & datastores
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, per-array pricing.

SAN recovery is priced per array and kept clear, with a free diagnostic and a written quote in hand before any work starts.

SAN & enterprise recovery
From £1,250 + VAT
From £1,250 + VAT and quoted per array — the disk count, RAID layout and the work involved all feed into it. No fix, no fee covers most jobs.
  • Free diagnostic and a written quote up front
  • Quoted per array, on disk count and layout
  • Every disk imaged read-only, your originals left untouched
  • LUNs, VMware datastores, VMs and databases all recovered
  • Verified data back on new storage sized to the volumes
// jobs off the bench

Recovered SANs, real jobs.

A selection of recent SAN jobs — offline pools, dead controllers, deleted LUNs and corrupt datastores. Identifying details stripped; every result verified.

// CASE 2026-039recovered
Dell EMC Unity · 24×1.8 TBRAID 5 poolPool offline

Dell EMC Unity whose storage pool had dropped offline.

Two disks in the pool had gone. We imaged all twenty, rebuilt the pool and its LUN, and recovered the volume.

// CASE 2026-033recovered
HPE 3PAR · 16×2 TBRAID 6Controller failure

HPE 3PAR that had lost both controllers.

Dead controllers, but the disks themselves were intact. We rebuilt the pool off the disks and recovered every LUN.

// CASE 2026-027recovered
NetApp FAS · 12×4 TBRAID-DPLUN deleted

NetApp production LUN deleted in error.

Barely anything had written over the blocks. We rebuilt the aggregate, re-mapped the deleted LUN, and recovered the data.

// CASE 2026-020recovered
Dell EMC VNX · 15×600 GBRAID 5VMFS corrupt

VMware datastore on a VNX LUN turned corrupt.

A damaged VMFS had taken the VMs offline. We rebuilt the LUN and its VMFS, then recovered and repaired the virtual machines.

// CASE 2026-013recovered
IBM Storwize · 20×900 GBRAID 10Failed rebuild

IBM Storwize corrupted partway through a disk rebuild.

The rebuild had written over part of the pool. We imaged every disk and reconstructed the array around the damaged region.

// CASE 2026-006recovered
iSCSI SAN · 8×2 TBRAID 5Power loss

iSCSI SAN corrupted by a data-centre power cut.

Write cache that never flushed had damaged the volume. We rebuilt the LUN and repaired the file system to recover the data.

// getting it to us

Two easy steps.

Send the affected pool's disks in for a free diagnostic with the array make, model and RAID layout; an engineer assesses them and confirms the exact per-array quote in writing before any work starts.

1

Send us your device

Getting your data back starts with getting the affected pool's disks — labelled in slot order — to us, with the array make and model. Pack them safely, enclose your contact details, and once we've run the free diagnostic we confirm your exact per-array quote in writing before any work begins.

How to pack it
  • Pack the pool's disks each wrapped anti-static and labelled with their slot order, in a sturdy carton with firm padding.
  • 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 array, RAID layout and fault on the form and an engineer will assess it and reply with a tailored per-array 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 SAN questions, answered.

The questions we’re asked most about recovering an enterprise SAN.

Usually, yes. An offline pool tends to mean several disks have dropped, or the pool metadata is corrupt — not that the data has gone. We image every disk, rebuild the pool and LUN layout, and reform the volume from the copies.

Usually not lost at all. Failed controllers never touch the data on the disks, and we don’t need them anyway. We image the disks, rebuild the storage pool and LUNs in software, and recover the volumes.

Often, yes, provided you move fast. A deleted or reformatted LUN usually keeps its data on the disks until something overwrites it — so stop writing to the array and we can re-map the LUN and recover it.

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

Enterprise SAN recovery opens at £1,250 + VAT and is quoted per array, since disk count, RAID layout and platform differ so much from one job to the next. A free diagnostic and a written quote always come before any work.

You always get a free diagnostic and a written, per-array quote first. SAN work carries a deposit against that quote, with the balance due only once the recovery has succeeded.

All of them — Dell EMC (Unity, VNX, PowerStore, Compellent), HPE (3PAR, Nimble, MSA), NetApp (FAS, AFF, E-Series), IBM Storwize and the rest, whether iSCSI or Fibre Channel. Since we rebuild off the disks, the platform seldom changes what can be recovered.

Usually not the whole chassis. Most of the time we need the disks from the affected pool, tagged with their slot order, plus the array make and model. After the diagnostic we’ll say precisely what to send.

Often, yes. A rebuild or expansion that failed usually leaves most of the original data intact beneath it. We image every disk in its current state and reconstruct the pool around whatever the operation overwrote.

SAN recoveries usually run one to two weeks. The span depends on the disk count, the RAID and pool layout, the file system, and whether any disk needs mechanical work on the clean-air bench.

Take the disks from the affected pool, label them with their slot order, and post them fully insured to the Guildford address — or arrange a drop-off. We’ll confirm exactly what’s needed once the diagnostic is done.

// san failed?

Pool offline, dead controllers or a lost LUN? We’ll recover it.

Free to diagnose, priced per array, and no fix no fee on the majority of jobs — every SAN recovered off the controllers, Dell EMC, HPE, NetApp and beyond. Get your recovery moving today.