Call us — 0191 406 1051
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →
/ home / devices / virtual machine
Devices · virtual machine recovery

Virtual machine data recovery in Newcastle.

Deleted virtual machine, corrupt virtual disk, broken snapshot chain or down datastore? We provide recovery services for virtual machines hosted on VMware, Hyper-V, Proxmox and many others. We’ll repair the virtual disk, rebuild the snapshot chain, and recover the data inside the VM, all without working on your original data.

From £800 · per VM
Most jobs — only pay if we recover your data
VMware · Hyper-V · +
!

Don’t keep running a host with a failing VM or datastore.

If you experience issues with a virtual machine that will not boot, if a snapshot chain breaks, or if a datastore is throwing errors, do not write anything else to this area. Attempting to consolidate your snapshots, attempting to retry a merge, or simply allowing the host to continue in operation could result in overwriting the exact information/data you need; additionally, turning on a VM using a corrupted datastore can exacerbate problems. Note the virtual machine ID along with the disk files and datastore being used. Do nothing else with the VM, files or datastore; leave all areas exactly as they currently exist. Contact us immediately. The initial attempt will be the safest.

// faults we recover from

Virtual machine faults we fix.

The main types of failure we recover from are deleted VMs, broken snapshots, corrupt or invalid disks and datastore issues.

⊟Deleted VM or virtual diskMistakenly deleted a virtual machine or one of its VMDK/VHDX files? In most cases, when a virtual machine is removed from a working datastore, the actual data remains intact until it is overwritten by some new operation. Immediately stop the host from writing to it and we should be able to build an exact replica of the disk and recover your VM.LogicalDeleted◌Corrupt VMDK or VHDXThe virtual disk for your VM has been corrupted, is invalid or simply refuses to open, therefore your VM won’t boot? We will repair the VMDK/VHDX file (descriptor, headers and grain tables) and recover the data contained within.DiskCorrupt◭Broken snapshot or checkpoint chainA broken, orphaned or unmerged checkpoint chain? Most often this causes loss of virtual machines; we build a new base and delta chain and get the VM running again.SnapshotChain◈VM won’t power on or invalidAn invalid, inaccessible or orphaned VM which fails to start? Usually the virtual disk is OK; we fix the config and disk and get the machine started.BootInvalid▦Corrupt datastore or volumeA corrupt VMFS datastore or CSV volume causing all VMs on it to go offline? We restore the datastore and get all VMs back online that sit on it.DatastoreVMFS⊘Failed consolidation or mergeA stalled or damaged checkpoint merge/snapshot consolidation? We stop, work from copies and rebuild the chain to get the VM back with its contents.MergeHigh risk▤Thin disk or sparse corruptionA thin-provisioned virtual disk whose grain tables or block map were damaged, causing data loss? We rebuild the mapping and recover the contents.ThinMapping◐Guest file system corruptAre you experiencing problems with an NTFS, ReFS or ext4 filesystem that resides within a virtual machine? If so, are you able to access the virtual disk itself? Then we will need to attempt to repair the file system in order to recover your data and databases.GuestFile system⊗Underlying storage failedHas a RAID, NAS (Network-Attached Storage) or SAN (Storage Area Network) which contains your VMs failed? If so, we will first need to rebuild the storage array. Once this is completed we will be able to recover the datastore and each of the individual VMs contained within it.StorageRAID
// platforms we take on

Every hypervisor. Every disk.

Do you have virtual machines created using VMware, Hyper-V, Proxmox, Citrix, VirtualBox etc.? Regardless of the virtualisation software you utilise, as long as the virtual disk is in some type of format we will be able to assist you. In other words, the specific platform you use will determine how we go about recovering your data and/or your VMs, not if we can assist at all.

VMware ESXivSphereHyper-VProxmox VECitrix XenServerXCP-ngVirtualBoxKVMNutanix AHVVMware WorkstationVMDKVHDXVHDVDIQCOW2VMFSCSVNFS datastorevSANSnapshotCheckpointThin ProvisionDifferencingraw

We currently support: VMware ESXi, vSphere, Workstation and Fusion · Microsoft Hyper-V · Proxmox VE, Citrix XenServer, XCP-ng, Oracle VirtualBox, KVM and Nutanix · VMDK, VHDX, VHD, VDI and QCOW2 · VMFS, NFS and CSV datastores · snapshots, checkpoints and thin-provisioned disks.

// how the recovery runs

How a virtual machine gets recovered.

Virtual machine recovery works on two levels (the virtual disk and the data within). Recovery of your virtual machines begins with the safe removal of your virtual disks from the datastore, followed by repair of the virtual disk and/or any snapshot chain. Once repaired, we can mount the virtual disk and begin recovering your guest operating system, databases and files from copies.

01

Free diagnostic

Provide details of your setup: hypervisor used, format of virtual disks used etc., which VMs were affected by what. Upon reviewing this information, we will provide a written quote typically inside 48 hours.

02

Secure the virtual disks

We make a read-only copy of all your virtual disk files (VMDK, VHDX, VDI or QCOW2). If the datastore or its underlying storage has failed, we rebuild that first so that nothing is written to your originals.

03

Repair failed storage or disks

Should the underlying RAID, NAS or SAN hardware have failed or a physical drive requires repair or imaging, we will complete those repairs and then provide a comprehensive image. In cases where a physical drive needs drive-level repairs, we will require 50% of the quoted price up front prior to commencement.

04

Rebuild the disk & chain

We repair the virtual disk containing the descriptor, the headers, and the grain tables and rebuild any damaged snapshot or checkpoint chain into a single disk.

05

Mount & recover the guest

We mount the repaired disk and recover the guest file system, whether it’s Windows or Linux, files, SQL and Exchange databases, and application data, while doing repairs as necessary.

06

Verify

We verify that the recovered virtual machines, files and databases can open and are intact before returning them to your possession.

07

Return your data

We deliver your recovered VMs and/or data, via new storage and ready to be imported back into operation.

// what we recover from

Every VM. Your data back.

Each virtual machine, from VMware and Hyper-V to Proxmox and all points between, is recovered through repair of the virtual disk, recovery of data in the virtual machines, and restoration of the snapshot chain regardless of what has happened to the host or to the data storage.

Every VM
VMware, Hyper-V +
Read-only
disks never altered
Disk & guest
both recovered
48 hr
Diagnostic turnaround
Snapshots
chains rebuilt
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? 0191 406 1051 · Mon–Fri 9am–5:30pm

// pricing

Plain, tiered pricing.

Pricing is clear and tiered, with a free diagnostic and written quote prior to starting any work.

Virtual machine data recovery
From £800 + VAT
For a single virtual machine (VM) or a virtual disk, on healthy storage, price from £800 + VAT. On a full datastore or host (multiple VMs), price from £1,200. In most cases you only pay if we recover your data.
  • Free diagnostic and a written quote first
  • Single virtual machine or virtual disk from £800 + VAT
  • Full datastore or host — multiple VMs — from £1,200 + VAT
  • Virtual disks copied read-only — your originals are never written to
  • VMs, databases and guest files recovered and verified
// jobs off the bench

Failed VMs, brought back.

Examples of recent virtual machine recoveries (identifying details removed): deleted VMs; broken snapshots; corrupt disks; failed datastores. Every result was verified.

// CASE 2026-037recovered
VMware ESXi · VMFSVMDKDeleted VM

Production VM deleted from an ESXi host by mistake.

The VMDK had been deleted from inventory, but its blocks were still stored. We rebuilt the VMDK and recovered the entire VM.

// CASE 2026-031recovered
Hyper-V · CSVVHDX · AVHDXSnapshot broken

Hyper-V VM that wouldn’t start after a checkpoint merge failed.

The AVHDX checkpoint chain had been broken. We rebuilt the AVHDX chain into one VHDX and recovered a consistent, bootable VM.

// CASE 2026-025recovered
VMware vSphere · VMFSDatastoreDatastore corrupt

VMFS datastore corruption that took six VMs offline.

A power outage caused a problem with the datastore. We rebuilt the VMFS and were able to retrieve all six virtual machines and their data.

// CASE 2026-018recovered
Hyper-V · 2×SSDVHDXCorrupt disk

Corrupt VHDX on a SQL Server VM that refused to mount.

The VHDX header was corrupt. We were able to fix the virtual disk and get the SQL databases that were in it back.

// CASE 2026-011recovered
Proxmox VE · ZFSQCOW2Failed migration

Proxmox VM corrupted during a storage migration.

The QCOW2 image was corrupted. We were able to fix that and restore the Linux guest and the application data.

// CASE 2026-004recovered
VMware ESXi · RAID 5VMDKArray failed

ESXi host whose underlying RAID 5 dropped offline.

The datastore was on a dead array. We rebuilt the RAID and retrieved both the datastore and all VMs on it.

// getting it to us

Two easy steps.

When you send the unit in for its free diagnostic, let us know what happened with the unit. An engineer will review the unit and confirm your quote in writing prior to starting on your recovery.

1

Send us your device

Before you post or drop off your device, please get a quote from us by phone or with the form. Once we receive your device, our recovery process can start. Safely pack your device, include your name and contact information within the packaging and ship it to us. After performing your free diagnostic, we’ll send you a written confirmation of the exact price of our services prior to starting any work.

How to pack it
  • Place the unit into a small sturdy box or a well-padded envelope.
  • It is okay to remove caddies, cables and power supplies since they are not required during the recovery process.
  • Your contact information (name, address, phone number, and e-mail) should be included in the box along with a note that indicates who sent it or by using our shipping form; then close it.
Post toNewcastle Data Recovery
Rotterdam House, 2nd Floor
116 Quayside
Newcastle NE1 3DY
⇣Shipping formPDF · print & include with your devicePDF ↓

If you decide to post it, we would advise using a trackable and insured postal service. Or if you prefer to drop it off, we are open Monday to Friday, 9am to 5:30pm, and you don’t need an appointment. Just pack the unit as described in step one before dropping it off.

2

Need more information?

Would you like a little more background information prior to sending it? Fill in the form to provide more details about your problem; an engineer will evaluate it and reply with a customised quote.

An engineer reviews every enquiry personally — we usually reply within 30 minutes during the day. Prefer to call? 0191 406 1051.

✓

Thanks — your message is in.

We’ll be in touch shortly. If it’s urgent, call 0191 406 1051.

// questions

Virtual machine recovery, answered.

Frequently asked questions about recovering a virtual machine.

Typically, yes, as long as you are quick about it. Once you have deleted your virtual machine (VM), its virtual disk blocks will normally remain in place until they are rewritten. If you stop the host from writing to the datastore before contacting us, we can rebuild your virtual disk and then restore your entire VM. The quicker you get back to us, the sooner you will be able to access your machine again.

Virtually never. In nearly all cases where a VM refuses to start up there is either a corrupted virtual disk, a broken snapshot chain, a missing configuration file or some other problem but typically the information stored within the virtual machine itself is fine. As such once we have repaired the VMDK/VHDX files and rebuilt any missing parts of the snapshot chain we should be able to recover both the machine and its contained information.

Yes, this is probably one of the most common reasons why a VM fails to run. When a snapshot or checkpoint chain is removed without being properly merged/combined, etc., the VM may refuse to boot up. We can take each individual delta disk and combine them into a single VMDK/VHDX virtual disk which will allow you to successfully boot up your VM.

Generally, yes. We restore virtual disks by repairing the descriptor, headers, grain table and block map at the format level for all formats (VMDK, VHDX, VHD, VDI and QCOW2) and then mount the disk and recover the guest file systems and data within the mounted disk.

A standalone virtual machine (VM) or virtual disk on healthy storage will start at £800 plus VAT. A complete datastore or host with several VMs will start at £1,200 plus VAT based upon both the storage and the amount of effort required. Each job begins with a free diagnostic and a written quote, and in most cases you only pay if we recover your data.

Yes, on most jobs. In cases where low-level repair of the disk will be required we require a 50% deposit up front to begin recovery services, however the remainder of the cost is only due after successful completion of the recovery service, therefore if we cannot complete your recovery then you would never have paid the remaining amount.

All platforms: ESXi and vSphere (VMware), Hyper-V (Microsoft), Proxmox, Citrix, VirtualBox, KVM and Nutanix; as well as all of the different formats of virtual disks: VMDK, VHDX, VHD, VDI and QCOW2. It is the platform that will decide how to proceed with recovery not if recovery can occur.

Yes. If you have lost the RAID, NAS or SAN that underlies your virtual machines, we first recover that underlying storage and then rebuild your datastore and each of your virtual machines on that rebuilt datastore. Both layers are ones in which we can assist.

Yes. We recover and mount the virtual disks and restore the guest operating systems including all of its files (Windows, Linux etc.) SQL Server/Exchange databases, app data and any other type of file; repairing as necessary and testing that files are accessible prior to their return to you.

When working with single VMs or disks, a 3 to 4 working day turnaround is generally achieved. In the case of a complete datastore or host or any job where the storage has failed, there’s a turnaround of 4 to 7 working days. A free diagnosis usually takes place in 48 hours while urgent jobs can often be given a priority.

When the storage is working properly, you can choose to send the disk files to us on a drive by post, or deliver them to us (fully insured) either by post or personally to our Newcastle location Monday to Friday, 9am to 5:30pm. For RAID disks, please label them with their bay number, and indicate your name, organisation, address, phone number, and email so that we can register them and give you a quotation before working on them.

// vm failed?

Deleted VM, corrupt disk or broken snapshot? We’ll recover it.

Diagnostic is free, our pricing is tiered with a minimum charge of £800. In most cases you only pay if we recover your data. All types of VMs can be recovered (VMware, Hyper-V, Proxmox etc.), all types of disks and data can be recovered. Start recovering now.