Enterprise storage stacks abstractions — disks into RAID groups, groups into pools, pools into thin-provisioned LUNs mapped to hosts. A fault in any layer hides the data behind it, and recovery means rebuilding each in order before a file system is even visible. That is why it is quoted as a project rather than a price.
$ bdr diagnose /dev/san → Array: Dell EMC Unity · 24 × 1.8 TB · RAID 5 → Status: POOL OFFLINE — 2 disks failed in pool → Client: confidential · Oxford OX2 $ 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
On enterprise storage the LUN layout, mappings and pool metadata matter as much as the disks. Export or photograph the configuration if you still can, and do not let the system rebuild, reinitialise or expand anything while a fault is unresolved.
SAN failures are rarely a simple disk problem — there are more layers, and any of them can be the fault.
The reason enterprise recovery is priced differently from a server array.
A SAN stacks abstractions: physical disks into RAID groups, RAID groups into storage pools, pools carved into LUNs, LUNs thin-provisioned and mapped to hosts, and often snapshots or replication above all of it. Each layer has its own metadata, and a recovery has to reconstruct them in order before any file system is even visible.
Add scale — dozens of members across multiple shelves, each needing imaging — and vendor-specific formats that are rarely documented, and the work is substantially larger than a single array. That is why SAN recovery is quoted separately and why the configuration information you can supply genuinely shortens it.
Assessed by architecture rather than badge.
Including Unity, PowerVault, MSA, 3PAR, FAS and Storwize families.
Including multi-path environments and units with expansion shelves.
VMware VMFS and Hyper-V volumes presented from SAN LUNs, and the VMs inside them.
Where a snapshot or a replicated copy is the surviving good state and needs extracting.
Older units where vendor support has ended and documentation is scarce — a frequent reason these reach us at all.
Priced separately from server and RAID work, because the job is materially larger.
SAN and enterprise storage recovery starts from £1,250 +VAT and is quoted after a scoping discussion rather than from a price list — member count, shelf configuration, vendor format and what has already been attempted all bear on it. A 50% deposit applies, with the balance payable on successful recovery.
Confidentiality is standard: NDAs signed as a matter of course, one named contact throughout, and data remaining in the UK. Tell us the vendor, model, LUN layout and RAID configuration at the outset — on enterprise work that information materially shortens the job.
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.
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.
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.
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.
We’ll be in touch shortly. If it’s urgent, call 01865 593000.
The questions we’re asked most about recovering an enterprise SAN.
There are more layers. A SAN stacks disks into RAID groups, groups into pools, pools into thin-provisioned LUNs mapped to hosts, often with snapshots above. Each layer has its own metadata and all of them must be reconstructed in order before a file system is even visible.
Usually. That pattern means the pool or LUN metadata has been lost while the underlying storage is intact — the data is present and the description of how it is carved up is missing. It can be reconstructed from images of the members.
Vendor and model, the RAID configuration, the LUN layout, and crucially what has already been attempted. On enterprise work that information genuinely shortens the job, and a configuration export or even a photograph of the management screen is valuable.
Yes — VMFS datastores and the VMDK files inside them, including where the LUN itself needs reconstructing first. Hyper-V volumes are handled the same way.
As standard, along with a single named contact throughout and data remaining in the UK. Most enterprise clients require this and we would expect it regardless.
From £1,250 plus VAT, quoted after a scoping discussion rather than from a list — member count, shelf configuration and vendor format all affect it. A 50% deposit applies with the balance on successful recovery.
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.