Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Trickier jobs / Server data recovery

Specialist · server data recovery

Server data recovery in Brighton. The server can be replaced by lunchtime. What it held can’t.

Data loss in server environments is seldom caused by 'dead' platters; rather than that, we see states of controllers that no longer trust their disks, arrays that can be destroyed with one wrong keystroke, caches that were never flushed. We recover using disk images and do so without needing a controller. In addition, we return volumes, virtual machines (VMs) and databases, the very items your company operates upon. Brighton servers travel as bare disks labelled for each bay, while the chassis remains secured to its respective rack where it was originally located. Get a quote first, by phone or with the form, then post the disks tracked and insured, or drop them off at our Guildford intake lab, Monday to Friday, 9am to 5:30pm (no appointment needed).

Only pay if we recover your data, on most jobs Free diagnosis & written quote Post-in from anywhere in Sussex

Talk it through with an engineer
01273 964902

What you're seeing, decoded.

Something else? Run the triage →
The problem as describedWhat it meansFirst thing we do
Foreign Configuration Detected (Dell PERC)The metadata on your disks does not match what is in the controller's memory: a safety halt, not a death noticeNeither Import nor Clear
1786: Drive Array Recovery Needed (HP)A rebuild is required or was interruptedPower down and image first
Amber lights after an event that caused a loss of power to the drivesWrites to cache and writes that were interrupted: the array's order lives on the disksDon't force drives online
Server boots, volume missingDamage to file system or controller state while intact data remainsHigh recovery odds
RAID card itself has diedArray geometry is stored upon members, not cardsNo matching controller needed
After 'recovery', the VMs and databases won't mountReturning files isn't the job done; consistency must be achievedSee our virtual machine and database pages
Getting it to us from Brighton: get a quote first by phone or with the form. And we will walk you through packing it. Then post your device tracked and fully insured to our intake laboratory at Guildford (free return postage), or drop it off there Monday to Friday, 9am to 5:30pm (no appointment needed). Details for sending are located on the contact details page.

Where server arrays keep their secrets.

Dell PERC & MegaRAIDWrite industry-format DDF metadata onto the trailing sectors of every member, which is why arrays are able to reconstruct from drive images alone on our bench, no PERC required.
HP Smart ArrayIt does things differently, and intentionally: it has a proprietary RIS block at the start of each disk, and parity offset by a stripe. Use generic 'RAID recovery' settings on an HP array and you will receive garbage.
The Import / Clear forkTwo buttons, both destructive when pressed at the wrong time: Import may inject stale metadata into live stripes; Clear will delete the map entirely. Prior to making a decision either way, all members should be imaged.
Write-back cacheHost-acknowledged writes that reside in controller memory, protected by battery or supercap. A power event mid-flush is the classic invisible corruption, and why 'it just lost power' cases require imaging, not optimism.

How we recover it, stage by stage.

01

Booked in, diagnosed free Free

Your device is logged under its own case reference as soon as it arrives. An engineer assesses the fault and confirms what is actually recoverable. And you receive a fixed price in writing: no diagnosis fee. No obligation. And no paid work until you say go.

Free diagnosisFixed written quoteNothing to sign
02

Freeze the state

Power down, label every bay, resist any prompt. All members (including those marked failed) are individually imaged using hardware tools before anything is interpreted.

Every member imagedFailed drives included
03

Reconstruct without the controller

Level, stripe size, order of drives and rotation of parity are determined through evidence presented by the DDF/RIS on the images; the array is virtually reconstructed, and a dead controller is an inconvenience, not a wall.

Geometry from the metadataController not required
04

Recover what the business runs on

The file system presenting on top (VMFS datastores, NTFS/ReFS/ext4/XFS) is restored during re-assembly, and the payloads that matter (VMs/databases/shares) are verified to actually mount, not simply exist.

Volumes repaired on the copyPayloads verified mounting
05

Verified, returned, signed off

You approve a full listing of everything that came back before you pay the recovery fee. Your data returns on new media with free return postage. And the case only closes once you have confirmed all items open on your side.

File listing approvalNew media includedFree return postage

What the lab checks first

  • DDF at the tail, RIS at the head: the knowledge of where each controller family keeps its map is the difference between reconstructing an array and guessing.
  • 'Failed' members are witnesses: a drive that the controller dropped weeks earlier still holds the most recent version of certain blocks of data. Re-assembly chooses per block.
  • HP's delayed parity is a deliberate trap for generic tools: HP sets parity off by one stripe, and its arrays only import on HP supported hardware. We rebuild it like they originally intended.
  • The cache battery is the unsung witness: whether or not the write-back cache was able to flush determines what condition the file system above will be in when we are done. We check this prior to making any promises.

Why the two-button prompt deserves its reputation: when the PERC performs an Import, it writes over the existing view of metadata being used at the time of import; when performing a Clear, it completely removes the DDF mapping from the drives. Each action is a single keystroke, irreversible once taken, and each becomes a risk-free question as soon as all disks have been properly imaged; this is why we choose to image first: it is our entire approach.

From the casebook.

EX · BDR-2026-0816CHECKED ✓

A ProLiant that survived the power cut but not the restart

A power outage occurred; the UPS exhausted its capacity and, upon rebooting, the Smart Array prompted users for decisions they could not safely make. All four members were successfully imaged, the RIS metadata was successfully read, delayed parity was honoured, and the practice management database was mounted for use from the rebuild, complete to the last pre-outage write the cache had flushed.

Database mounted clean5 days in lab

Before it reaches us.

Do

  • Take power off and take photos of the controller screen first
  • Mark each drive with its bay position before removing it
  • Before sending us any parts, get a quote, then send all members of the RAID set: failed members also contain evidence
  • Let us know what was running on this box: VMs, SQL, Exchange, shares etc.

Don't

  • Choose either Import or Clear at the foreign-config prompt
  • Pop in a spare disk and let a rebuild begin
  • Update the controller firmware during a job
  • Use this server until the data is safely replicated somewhere else

Asked on this bench, answered honestly.

My server won't boot — is the data gone?

Not usually. The majority of server issues are due to a faulty controller state, incorrect array metadata or a damaged filesystem while leaving the actual disks unscathed. Turn off power, shut down all prompts, and the chances of success remain very strong.

What does 'Foreign Configuration Detected' actually mean?

The Dell PERC will identify an error condition when reading the metadata stored on the disks which does not match what it believes should be there after a new board is installed, the drives are physically relocated or a controller fails. This is a built-in 'safety' delay. Both choices available on-screen can result in loss of data; imaging first will allow you to make a safe choice.

Can you recover the array without the original controller?

Yes. PERC and MegaRAID store standard DDF metadata on each disk that identifies the geometry of the array. HP uses its own RIS blocks; we can still extract the geometry from these blocks once we have imaged the disks. We can also recreate the original configuration without having to use another identical adapter.

Do you handle the VMs and databases too, or just files?

Both, and it matters. Getting your .VMDK or .MDF files restored is only part of the battle; getting the hypervisor or database engine to accept that restore is the other half. Our VMware and database sections address that level.

Whatever's failed, don't power it on again.

Each time a damaged device starts up again, data is lost. Open a case first; the diagnosis is free either way.

01273 964902