Home / Devices / SAN

SAN Data Recovery Staines

Everything that is connected to your SAN will go down if shared storage fails. We recover SAN environments (failed LUNs, corrupted VMFS volumes, broken storage pools) for businesses and IT service providers throughout Surrey and west London.

▲

Free diagnostic with every SAN job. One fixed price in writing before we begin our work.

In most cases you only pay if we recover your data. For all electronic and mechanical work, including chip-level repairs, 50% is required upfront, with the balance only payable if we recover your data. For BitLocker, ransomware, CCTV/DVR and forensic jobs, full payment is made upfront once you accept the fixed quote. Full details regarding our costs can be found on the data recovery cost page.

// top 12 faults we recover from

The twelve ways they fail

The first step of every SAN job is to match the fault to the symptoms: almost everything that comes into the lab falls under these twelve categories of faults.

Multi-drive failure in a RAID group

Enterprise shelves often lose several drives at once rather than one at a time, so each affected drive is repaired and imaged on its own first.

LUN offline or corrupted

The block device your servers were using has gone; it is rebuilt from the pool metadata up.

Storage-pool metadata corruption

When the map that turns blocks into LUNs breaks, we rebuild it from the raw structures on the disks.

Failed firmware / controller update

When an update bricks a controller pair, there is still good data on the drives, stranded because the management layers no longer answer.

Both controllers failed

Both controllers fail together more often than the datasheets suggest, and then recovery goes straight to the drives.

VMFS datastore corruption

The VMware layer may crash while there is nothing wrong with the LUNs underneath; the datastores and VMDKs are read out and repaired.

Deleted or reformatted LUN

A provisioning mistake takes seconds; how much we can recover depends on what was written on top afterwards.

Broken snapshot chains

If you lose just one link in the chain, a snapshot-dependent volume collapses; we rebuild the chain at image level.

Thin-provisioning overrun

When a pool runs out of real blocks, it quietly corrupts every thin volume sitting on it.

Cache / battery write-hole

A power event while the cache battery is dead leaves parity and data out of step across the whole group.

NetApp / Dell EMC aggregate loss

When a NetApp aggregate or Dell EMC pool fails, its LUN map is lost; we rebuild it from the raw RAID-group structures up.

528-byte sector drive handling

Enterprise drives formatted to 520/528-byte sectors confuse standard tools, so we image them natively on the SAN fabric.

Enterprise storage, properly handled

The problem is complex because of how SANs are stacked: physical drives in RAID groups, those groups put together as a pool of storage that is carved into LUNs, and finally a file system or hypervisor datastore layered on top (commonly Dell EMC, HP MSA/EVA, IBM, NetApp or Fujitsu hardware). The recovery process works in reverse: we start at the bottom of the stack by imaging the physical disks, build the RAID groups back up from the disk images, then reconstruct the pool metadata. Once we have recovered the LUNs we can extract the virtual machines or databases inside them. In-house IT teams and MSPs work with us on these jobs all the time, and we follow your change-control and confidentiality requirements throughout.

It's the VMs that matter, not the blocks

Remove all the storage jargon and virtually every SAN job is a VM job: what the customer wants is three critical servers up and running again, not a petabyte of raw blocks. We extract VMDK or VHDX files from the rebuilt datastores, fix those files when necessary, and, to get the business operational as quickly as possible, we can prioritise specific databases (SQL/Exchange) before the full recovery is complete.

// the equipment we use

A professional lab, not software guesswork

Half of SAN recovery is merely being able to physically connect the device, so connectivity is just as important as the recovery stack:

FC / SAS / iSCSI lab fabric

We connect directly to enterprise storage shelves and drives using our native HBAs and interposers, with support for 520, 524 and 528-byte sector formats included.

Parallel enterprise imaging

All members of a RAID group are captured at once, and any failed member is repaired on the PC-3000 bench prior to joining the recovery run.

Pool & LUN reconstruction tools

The vendor metadata is parsed and rebuilt in strict sequential order: RAID groups, then pools, then LUNs, then file systems.

VMFS / VMDK / VHDX parsers

Once reconstructed LUNs have been mounted as datastores, each virtual disk is removed from the datastore and repaired individually.

Database-aware extraction

For critical SQL Server, Exchange and similar workloads, we verify them and move them to the front of the queue so that critical services recover first.

Write-blocked workflow throughout

Every original drive and shelf brought into the facility remains read-only until the customer takes their unit(s) back.

// manufacturers & models

Top SAN manufacturers we recover

Dell EMCHPENetAppIBMLenovoFujitsu ETERNUSHitachi VantaraPure StorageSynology / QNAP (rack)Seagate / Dot Hill

Systems on the bench most often

If you do not see your platform listed above, it's likely still familiar: most enterprise storage solutions reuse the same building blocks under different brand names. An aggregate failure on a NetApp system or a pool failure on a Dell EMC system causes loss of the LUN mapping, which is recovered from the raw RAID groups upward. In some cases both controllers on Fujitsu ETERNUS and HPE MSA shelves fail, so recovery proceeds directly to the individual drives. In addition, enterprise disks formatted to 520/528-byte sectors are imaged natively rather than fought with standard tools.

// before you post it

Sending it in — remove the drive if you can

Label each drive with the shelf and slot location it was removed from, before it leaves the rack. Enterprise arrays rely entirely upon the drive order and layout being correct in order to function. Once a quote is obtained (call 0800 689 0668 or use the free online diagnostic), post us just the labelled drives (photos of how it was configured help a lot); shelving units and controllers do not need to be sent.

// getting your device to us

Post your device to us — it's simple

Before sending anything, get a quote from us either by telephone or using our free online diagnostic. Then post your hardware to us (tracked and insured), or drop it off at our Guildford laboratory in person.

Sending a drive from a computer, laptop, MacBook, iMac, CCTV/DVR or server? You will need to remove the internal hard drive or SSD and send us just the drive, as we are unable to remove the drive for you. We also cannot recover storage soldered onto a motherboard, such as in Apple Silicon Macs and some thin laptops. Only drives that can be removed from a machine and sent to us can be recovered. If you are unsure whether your device has a removable drive, please call us before sending. RAID, server and SAN drives need to be removed from their enclosure and labelled by bay. For a NAS, send the disks themselves if they are removable, otherwise the entire NAS device. An external single drive should come to us whole, along with its cable and power supply.

  • Wrap your hardware in bubble wrap or a padded envelope. There's no need to include cables or power supplies, unless you're sending an external drive, which should come whole with its own.
  • Download, print and complete the booking-in & shipping form (PDF) and enclose it, with your name, contact number, and a short description of what has happened.
  • Post your hardware by way of Royal Mail Special Delivery, or alternatively choose a tracked courier service of your preference, to ensure full coverage of loss/damage during delivery.
  • Would you rather deliver it personally? Just bring it into the Guildford lab's reception, at the address shown, Monday to Friday, 9am to 5:30pm. A prior appointment is not necessary.
// send your device to your nearest location

Guildford Data Recovery

Building 2, Ground Floor
Guildford Business Park
Guildford, GU2 8XH

↓ Print the booking-in & shipping form (PDF)

Please mark the package for the attention of Guildford Data Recovery, and we will call you as soon as we have diagnosed your media.

Unsure as to how to proceed with sending the item in for recovery? Then simply call 0800 689 0668, or complete the free online diagnostic prior to dispatching the item to obtain your price quotation.

// san recovery questions

Common questions

Freeze all writes to the platform and don't reinitialise anything. Call us with what you know about the make, model and layout, and we will guide you through removing the drives and labelling them by bay, so only the drives come into the lab and the shelving units and controllers remain on site.
Yes. Rebuilding LUNs and recovering the VMFS layers above them is one of the most common types of work we undertake for enterprise platforms. We extract the VMs you require first, allowing you to start up your critical services quickly.
Absolutely. We can work under NDA, follow your change-control process and hand back to your IT team to restore their systems once the data has been recovered.
Diagnosis of business-critical storage is our top priority the moment it arrives at our facility. If it is business-down, please let us know when you call 0800 689 0668. This allows us to plan the quickest safe route for getting the drives to our Guildford lab: tracked, fully insured next-working-day post, or, if you prefer, you can drop the drives off at the Guildford lab's reception (Monday to Friday, 9am to 5:30pm, no appointment needed).
// related services

Also recovered here

Ready when you are.

Free diagnostic, fixed quote, and in most cases you only pay if we recover your data. Start now or call the freephone.