We can recover your virtual machine from deletion, a corrupt virtual disk, a broken snapshot chain or a datastore that’s down. We work with VMware, Hyper-V, Proxmox and beyond, and on both layers of the virtual machine. The virtual disk file comes first: once we have fixed its descriptor, headers and snapshot chain, we mount it to recover the guest file system and everything inside it.
Is a machine no longer booting, has a snapshot chain broken, or is there an error on the datastore? Stop writing to it straight away. Every time you consolidate a snapshot or retry a merge, and every hour the host stays up, you are taking the risk of adding new data on top of the data we are trying to restore, and booting a machine off a damaged datastore is worse still. Before calling us, write down which virtual machines were affected, the disk files associated with them and which datastore they reside on, then leave all of it untouched. The first recovery attempt is the safest one.
Most of the issues we receive relate to deleted machines, corrupted disks, broken snapshot and checkpoint chains, and datastores stranded on failed storage.
Not a single virtual machine is outside our scope (VMware, Hyper-V, Proxmox, Citrix, VirtualBox and the rest), whatever the virtual disk format. Whatever hypervisor you use, we recover the disk file and the guest inside it.
Nutanix, KVM, Oracle VirtualBox, XCP-ng, Citrix XenServer and Proxmox VE; Microsoft Hyper-V; VMware ESXi, vSphere, Workstation and Fusion · QCOW2, VDI, VHD, VHDX and VMDK · CSV, NFS and VMFS datastores · thin-provisioned disks, checkpoints and snapshots.
Send us your virtual disk files for a free diagnostic (with details of your hypervisor, the format and what went wrong), and an engineer will review them and confirm the exact cost in writing before any work begins.
Walk us through what happened: which hypervisor, what disk format is being used and where things went wrong on which machines. An engineer will assess your situation and provide a written quote, typically within 48 hours.
Before doing anything else, we copy the disk files (be they VMDK, VHDX, VDI or QCOW2) read-only. This way, we do all our work on those copies, and your original files are never touched.
If there’s an issue with the underlying storage, whether it’s a failed array, NAS or SAN, or a physical drive that needs some bench time, that comes first. That means repairing and imaging the drive, or rebuilding the array, so that we start from clean disk files.
Then we go through the process of making the disk correct again, including the grain tables, headers and descriptor. In addition, we fold any broken snapshot or checkpoint chain back into a single consistent disk.
Next up is mounting the repaired disk, then pulling out the guest file system with everything on it, whether Windows or Linux: application data, Exchange and SQL databases, and files.
Nothing leaves our lab until we have opened the recovered virtual machines, files and databases and confirmed they are complete.
Once that’s done, we return your machines (or just the data pulled out of them) on new storage, ready for you to import and boot straight away.
Post the disk files or bring them in. We perform a diagnosis before quoting, and in most cases you only pay if we recover your data.
Tell us what happened and we’ll get back to you, usually within a working day.
We’ll be in touch very soon. If it can’t wait, call 01483 901310.
The cost structure for recovering your virtual machines follows a simple tier: you get the diagnostic at no charge and a written quote before we take a single step.
Here are some examples of recent virtual machine recoveries: deleted machines, broken snapshots, corrupted disks and failed datastores. Identifying details have been removed, and every result has been verified.
Although the machine was gone from the inventory, its VMDK blocks remained on the datastore. The disk was then carved back out and the machine recovered.
The AVHDX checkpoint chain was broken, so we collapsed it back down into a single consistent disk. The machine came back online and was recovered.
When a power cut hit the datastore, it was left damaged. We rebuilt the VMFS and recovered all six machines.
The damage was in the VHDX header. After repairing the disk and mounting it, we were able to access the SQL Server database inside and recover it.
The migration had left inconsistencies in the QCOW2 image. We rebuilt the image and recovered both the guest and its data.
A failed array caused the datastore on it to fail. After rebuilding the RAID 5, we were able to recover both the datastore and every machine sitting on it.
Send the virtual disk files to us for a free diagnostic, with the hypervisor you are running, the format and what happened. An engineer will assess them and confirm your exact quote in writing before any work is carried out.
To get your data back, you must first send us the virtual disk files (or the failed storage that holds them) safely. Please also tell us which hypervisor you are using, along with the format. Once we have run our free diagnostic, we will confirm your exact quote in writing before any work begins.
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.
Do you want a scoped quote first? Just fill out the form with details of the hypervisor, disk format and fault, and an engineer will assess it and reply with your customised quote.
We’ll be in touch shortly. If it’s urgent, call 01483 901310.
The questions about recovering virtual machines that our customers ask most often.
Often, yes, provided you move fast. A deleted VM’s virtual disk blocks usually stay on the datastore until something overwrites them, so there is likely enough time for us to carve the original VMDK or VHDX back out. Stop powering VMs on and we can recover your deleted VM.
Usually nothing is lost. A machine that cannot boot nearly always has a corrupted disk, a broken snapshot chain or a failure on the datastore, rather than missing data. We repair and recover the disk file first, then the guest inside it.
Yes, this type of recovery work is routine for us. When a snapshot or checkpoint chain breaks (delta VMDKs, or AVHDX files on Hyper-V), the data is split between the individual files, and we collapse the chain back down into one consistent disk before bringing the machine back.
Often, yes. The structural elements of the disk (grain tables, headers and descriptor) are repaired, then the disk is mounted so that the guest file system and everything contained within it can be recovered.
We operate on a tiered basis: a single VM or virtual disk is priced from £800 + VAT, whereas a full datastore or host containing multiple VMs is priced from £1,200 + VAT. Both begin with a complimentary diagnostic and a written quote.
Every virtual machine recovery job starts with a free diagnostic and a written quote. For VM work and any underlying storage recovery, we require a deposit based on that quote, and the final balance is only due if the recovery is successful.
All of them: ESXi and vSphere (VMware), Workstation and Fusion (VMware), Hyper-V (Microsoft), Proxmox VE, XenServer (Citrix), XCP-ng and VirtualBox (Oracle), and the disk formats VMDK and VHDX, VHD, VDI and QCOW2. No matter what created it, we can repair the disk and recover the guest.
Yes, both layers are covered. The failed drive is repaired, or the array/NAS/SAN rebuilt, so the disk files will be clean. Then the machines can be repaired and the data recovered.
Yes. The guest file system and the data it holds (files, Exchange or SQL databases, application data) will recover like any other volume once the disk is repaired and mounted. Repairs may be needed, depending on the extent of the damage.
Most VM recoveries are completed within a few working days. A full datastore or host, extensive corruption, or an underlying storage failure that needs to be rebuilt first will all extend this timeframe.
To start the recovery process, either copy the virtual disk files to a separate drive and send that to us, or, where the storage itself has failed, send the drives, NAS or server. Post these fully insured to our Guildford address, or drop them in on weekdays between 9am and 5:30pm. For smaller VMs, ask us about a secure upload.
We offer free diagnostics and charge by tiers starting at £800, and in most cases you only pay if we recover your data. Every virtual machine recovered, including disk and data, from VMware, Hyper-V, Proxmox and beyond. Get your recovery started today.