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 / VMware & virtual machine recovery

Specialist · VMware & virtual machines

VMware data recovery, Brighton. A virtual machine is four problems wearing one trench coat.

When a virtual machine fails, it may be due to a failure in one of four different levels: the RAID level, the VMFS data store, the VMDK files or the guest file system. Recovery requires a bottom-up approach where each layer is rebuilt using an image prior to accessing the next layer. No ESXi host, vCenter, nor any other matching equipment is required for successful recovery. Brighton hosts stay put: once quoted by phone or through our quote form, simply send your array’s disks labelled by bay, posted tracked and insured, or drop them off at our Guildford intake lab, Monday to Friday, 9am to 5:30pm (no appointment needed), and no other hardware components need to leave your rack.

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
Deleted VM from the datastoreVMDK blocks persist until reallocated on the VMFS volumeStop provisioning immediately
Cannot open the disk: parent has been modifiedSnapshot-chain CID mismatch: child and base do not agreeDo not force it: chains will break
Datastore is inaccessible after a RAID eventStorage layer failed; the VMFS above is usually repairableBottom layer first
The backup job leaves a phantom locked snapshotDelta files orphaned mid-consolidationCommon, and recoverable
Hyper-V VM dead after checkpoint mergeBroken AVHDX chain: binary structures, not textVerify parents before merging
The VMDK is back but the Windows inside won’t bootLayer four: repairing the guest file system on its ownHalf-done isn't done
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.

The four layers, bottom to top.

Layer 1 — the storageThe RAID or disk below it all. It is the first to be treated, by our server and RAID 5 playbooks, because a lying block device will prevent any datastore repair.
Layer 2 — VMFSThe clustered file system of VMware, parsed from the image at fixed locations (one-megabyte blocks on modern versions). Unlinked deleted VMs are located here, not removed.
Layer 3 — the VMDK pairVirtual disks are a small text description plus a large flat/delta extent. A hypervisor refuses a perfect disk based upon a one-line descriptor error. For this reason descriptors are changed while flat files are always left in place.
Layer 4 — the guestWithin the recovered VMDK exists an ordinary NTFS, ext4 or XFS volume with ordinary problems. The file system is repaired as you would repair any file system, on the recovery copy, and only then does "recovered" mean bootable.

How we recover a VMware datastore, 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

Stabilise the bottom layer

As we describe on our server pages (the physical storage is imaged and, if required, the array reconstructed), all of the higher layers are built upon the read-only images that were created.

Storage imaged firstArray rebuilt virtually
03

Parse and extract

From the image we parse the VMFS or NTFS datastore, locate deleted and live VMDKs and map snapshot chains, verifying CID and parent link relationships prior to stitching them together.

VMDKs extractedChains verified, not forced
04

Make it mount, then make it boot

The descriptors are fixed, the chains are consolidated correctly, and the last thing done is to fix the guest file system inside. The job is only signed off once the VM’s data has mounted, and not simply because there are files.

Descriptors repairedGuest 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

  • Deleted means unlinked: a quiet datastore keeps deleted VMs perfectly intact. A busy datastore will overwrite the deleted VM with the next provisioning job. Freeze first. Grieve later.
  • Descriptors are the fuse box: kilobytes of text that determine if terabytes of storage mount. We fix descriptors. We never touch the flat extents that they describe.
  • Backup software is a frequent co-conspirator: orphaned snapshots and phantom locks from jobs that were interrupted are responsible for a healthy share of the cases of "VMware corruption".
  • VHDX logs its own crashes: the internal log structure used by Hyper-V means power loss cases often self-document. Reading that evidence will always be better than guessing every time.

Why bottom-up isn't pedantry: a virtual machine’s data passes through four layers of ownership (blocks on physical media, VMFS, VMDK, guest file system) and repairing at the wrong layer writes fiction into all of the layers above it. Therefore, the professional sequence is as boring and absolute as possible: image, rebuild, parse, extract, repair, mount. Every single time. Because this is the only order that can’t destroy anything.

From the casebook.

EX · BDR-2026-0846CHECKED ✓

Two production VMs, deleted on a Friday, provisioned-over by nothing

A script written by an administrator to clean up had taken the wrong folder. Since the datastore was quiet all weekend both VMDKs sat unlinked and whole. Both machines booted in a sandbox by Tuesday evening after being parsed out of the VMFS image on Monday with their descriptors rebuilt. Payroll among them.

Both VMs booted3 days in lab

Before your VMware disks reach us.

Do

  • Lock down provisioning on the datastore immediately
  • Take note of snapshot history and backup software being used
  • Obtain a quote first, then send or image all underlying LUN drives, labelled by bay
  • Provide information on what guests run: this sets verification

Don't

  • Create anything new on the affected datastore
  • Edit a -flat.vmdk manually under any circumstances
  • Forcibly consolidate or delete snapshots to "clean up"
  • Assume that a restored file equals a bootable VM

Asked on this bench, answered honestly.

Can you recover a deleted virtual machine?

Yes, frequently: deleting a VM unlinks its files from the index of the datastore while the blocks persist until new provisioning claims them. Lock down the datastore, image the storage, and the VMDKs are usually parse-able out whole. Speed in freezing is the only game that matters.

What does 'the parent virtual disk has been modified' mean?

It's VMware's snapshot chain failing a paternity test: the parent ID recorded for the child delta does not match the base disk. Usually this occurs after a partial consolidation or restore. The chain is repairable at descriptor level; however, forcing the IDs to match regardless of "why" is how intact chains are reduced to lost data.

Do you need our ESXi host or vCenter to recover?

No. Everything we do is based on images of your data in storage on our bench (VMFS is parsed, VMDKs are pulled out, guests are repaired), and nothing will run on your systems until you decide that it should. A dead server does not impact the ability to recover.

Is Hyper-V the same process?

Same philosophy, different grammar: VHDX files with their own internal logs (binary) and AVHDX checkpoint chains which require verification of parent links using PowerShell, as opposed to a text editor, prior to merging. The discipline is identical: layers first, images only.

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