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.

We get your volumes back from an offline storage pool, controllers that have died, a LUN that disappeared or a corrupted datastore, on enterprise SANs from Dell EMC, HPE, NetApp, IBM and others, over iSCSI or Fibre Channel. The volumes are rebuilt from the disks up: every disk in the affected pool is imaged, the RAID groups, storage pool and LUN layout are recreated, and then the file system is rebuilt on top.

Quoted per array
Most jobs — only pay if we recover your data
Fibre Channel · iSCSI
!

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

A pool has gone offline, a controller has died or a rebuild has stalled? Stop. Do not run a rebuild, re-initialise or re-sync, as each of these lays down new writes that can smother the data we need, and creating a new storage pool or LUN may destroy the very map that locates it. Pull the plug on the SAN. Note which shelf and slot each disk came from. Then contact us. That first attempt carries the lowest risk of losing data, so it should be ours.

// faults we recover from

The SAN failures we take on.

Most SAN work that comes to us involves offline pools, corrupt datastores, dead controllers, deleted or reformatted LUNs, failed rebuilds and expansions, and corrupted VMFS datastores.

⊗Pool or RAID group gone offlineOnce a pool or RAID group loses more disks than it can carry, all LUNs associated with it go offline. We then image every disk and recreate the pool from those images to return the volumes.PoolOffline◌LUN deleted, unmapped or reformattedHas someone accidentally wiped, unmapped, trespassed or reformatted a LUN? The underlying blocks are usually still intact: we rebuild the LUN from the pool and recover whatever it held.LUNDeleted▤Storage processor or controller downA failed storage processor or controller can leave the SAN unable to present its volumes, even after failover. We extract the configuration, image the disks and rebuild the LUNs away from the failed hardware.ControllerSP◭Rebuild or expansion that failedA disk rebuild or a pool expansion that stalled or damaged the array. Rebuilds and migrations are where SANs are most often lost, so we halt the process, image every disk and then reconstruct the array from these images.RebuildHigh risk◈VMFS datastore or VM won’t startA VMware datastore on a SAN LUN corrupted, or virtual machines that will not start? We rebuild the LUN, fix the VMFS corruption and recover the VMDK files along with their data.VMFSVMs▦Pool metadata or thin-provisioning damageAfter a failed disk or a power cut, the mapping tables that locate your data within the array (the pool metadata and the thin-provisioning map) can become corrupted. We rebuild that mapping and piece the original LUNs back together.MetadataThin◎Firmware or array-OS update gone wrongA firmware or array-OS update that bricked the controllers or lost the configuration? Since the disks still hold your data, we read it off them and rebuild the LUNs without using the array hardware at all.FirmwareUpdate◐Power loss or write-cache corruptionOne data-centre outage can drop shelves and controllers at the same time, and any write cache not yet flushed corrupts the LUNs as it goes. In this scenario, every disk is imaged and then the volumes are rebuilt to their last consistent state.PowerCache⊘Disks or shelves in the wrong orderDisks moved between slots, or a shelf removed during a fault? We determine where each disk belongs in the pool and then rebuild the array using the correct arrangement.OrderShelves
// SANs we take on

Any array. Any LUN.

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

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 to us for a free diagnostic, with the make, model and RAID layout of your SAN. An engineer will inspect the disks and put the exact per-array figure in writing prior to commencing any work.

01

Free diagnostic

Tell us about the array (its make and model, the RAID layout, the number of disks and what failed) and an engineer will assess it and send a written quote, usually within 48 hours.

02

Image every disk

Working on dedicated hardware, we take read-only images of every disk from the affected pool, failing ones included, and then run all our work off these images. This way your original disks remain untouched.

03

Repair failed disks

In cases where a disk has failed mechanically or on its electronics, it is placed on our bench for new heads or a rebuilt board. The goal is only to let the engineer capture an image of the disk, and no more.

04

Rebuild the pool & LUNs

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

05

Recover the file system

Once the LUNs are restored, the file system on top (ReFS, NTFS or VMFS) is rebuilt and your virtual machines, databases and files are retrieved. Any damaged VMs or databases are repaired as required.

06

Verify

No data is returned to you 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 sized to the volumes, configured to go straight back into service.

// what we recover from

Any SAN. Recovered.

Post us the failed disks or drop them off. We provide a diagnosis followed by a per-array quote, and in most cases you only pay if we recover your data.

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 clearly defined, with a free diagnostic and a written quote provided prior to beginning work.

SAN & enterprise recovery
From £1,250 + VAT
From £1,250 + VAT, quoted per array depending on the disk count, RAID layout and scope of work. In most cases you only pay if we recover your data.
  • 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 corrupted datastores. All identifying information has been removed and 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.

In this job, two disks in the pool had gone. All twenty disks were imaged, the pool and its LUN were rebuilt, and the volume was recovered.

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

HPE 3PAR that had lost both controllers.

Both controllers were dead, but the disks themselves were still good. We rebuilt the pool using the disks and recovered every LUN.

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

NetApp production LUN deleted in error.

Almost nothing had been written over the blocks where the data was located. We rebuilt the aggregate, remapped 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 caused the VMs to go offline. The LUN was rebuilt, and so was its VMFS, after which the virtual machines were recovered and repaired.

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

IBM Storwize corrupted partway through a disk rebuild.

The rebuild had overwritten part of the existing pool. We created images of every disk in the pool and then reconstructed the array around the damaged area.

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

iSCSI SAN corrupted by a data-centre power cut.

The write cache had never flushed, causing damage to the volume. The LUN was rebuilt and the file system repaired to recover the data.

// getting it to us

Two easy steps.

First, send in the affected pool’s disks for a free diagnostic, with your SAN array’s make, model and RAID layout. An engineer will assess the disks and confirm the exact per-array quote in writing before any work starts.

1

Send us your device

To start recovering your data, we need to receive all of the disks from the affected pool, labelled by slot number, along with the manufacturer and model of your array. Pack the disks securely and include your contact information. After we complete the complimentary diagnostic, we will confirm your exact per-array quote in writing before any work begins.

How to pack it
  • Wrap each of the pool’s disks in anti-static wrap, label each one with its slot order and place them in a sturdy box with firm padding.
  • There’s no requirement to include anything else such as caddies, cables or power supplies since they’re not necessary for the recovery.
  • Include your personal contact information inside the box (your name, address, telephone number and email) on a sheet of paper or using our shipping form. Then simply close the package.
Post toGuildford Data Recovery
Building 2, Ground Floor, Guildford Business Park
Guildford GU2 8XH
⇣Shipping formPDF · print & include with your devicePDF ↓

Sending it by post? We’d recommend a tracked, insured service. Dropping it in? No problem: Monday to Friday, 9am to 5:30pm. Please package the device as described above first.

2

Need more information?

Need a scoped quote first? Describe the array, its RAID layout and the fault on the form, and an engineer will review it and send 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 are most frequently asked about recovering an enterprise SAN.

Usually, yes. An offline storage pool typically means several disks have dropped out of the array or the pool’s metadata is corrupt, not that the data has gone. We image every disk, rebuild the storage pool and LUN layout, and then use those copies to rebuild the original volume.

Usually, none of your data is lost. A failed controller never touches the data on your disks, and we don’t require your controller for a recovery anyway. Instead, we image your disks, rebuild your storage pool and LUNs in software, and recover your volumes.

Often, yes, if you act quickly enough. A deleted or reformatted LUN usually keeps its data on the underlying disks until something overwrites it, so stop writing to the array and we can remap the LUN and recover it.

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

Our enterprise SAN recovery starts at £1,250 + VAT and is quoted individually for each array, since disk count, RAID layout and platform differ so much from one job to the next. Before any work, we always provide a complimentary diagnostic and a written quote.

You always receive a complimentary diagnostic and a written, per-array quote first. SAN work carries a deposit against that quote, and the balance is only due upon successful completion of the recovery.

All of them: Dell EMC (Unity, VNX, PowerStore, Compellent), HPE (3PAR, Nimble, MSA), NetApp (FAS, AFF, E-Series), IBM Storwize and the others, whether via iSCSI or Fibre Channel. Because all of our recoveries are rebuilt from the disks, the platform seldom changes what can be recovered.

Usually not the entire chassis. Most of the time we need the disks from the affected pool, tagged with their slot order, along with the make and model of the array. Following our diagnostic, we will tell you precisely what to send.

Often, yes. When a rebuild or expansion fails, it usually leaves most of the original data intact beneath it. We image every disk in its present condition and then reconstruct the pool around whatever the operation overwrote.

SAN recoveries generally take one to two weeks. The time frame depends on how many disks are involved, the RAID and pool layout, the file system, and whether any disk needs mechanical work.

Please remove the disks from the affected pool, label them with their slot order and post them fully insured to our Guildford address, or arrange a drop-off. Once the diagnostic is done, we will confirm exactly what we need.

// san failed?

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

Free to diagnose, priced per array, and in most cases you only pay if we recover your data. Every SAN is recovered off the controllers: Dell EMC, HPE, NetApp and beyond. Get your recovery started now.