Read the relevant page, build a recovery brief, call an engineer, or send the case securely, without opening a second popup.
Problem, device and brand cards are normal page links. The assessment button builds a saved recovery brief.
Choose the closest description. If you arrived from a problem card, this step is already complete.
Brand, model family, exact model and capacity improve the handoff to the correct engineer.
Tick everything that applies. “Other” fields are available where the usual choices do not fit.
This is an intake guide, not a remote diagnosis or guarantee. The laboratory confirms the method, quote and limitations after assessment.
Read the recovery method, limitations and intake process for this device or issue.
Read the relevant pageBest for uncertainty, dangerous batteries, active incidents, legal deadlines and Emergency 24/7.
Call 1300 806 557Keep the menu open and load Wildfire’s secure submission form in this same full-screen panel.
Save the structured summary for a call, email, internal approval or later submission.
★ 4.8 · 96 Google reviewsBrisbane laboratoryAustralia-wide mail-in
One failed datastore can stop every server on the host. Let’s get the VMs back.
We recover VMware ESXi, Hyper-V, Proxmox and KVM virtual machines when the datastore, the snapshot chain or the RAID underneath has failed. Every disk is imaged first, and all the work is done on the copies, so your original storage is not written to.
See what decides the costFour servers, one datastore.
Each virtual machine is a set of files on one shared datastore, and the datastore is a single volume on the host’s RAID. Every drive in the host holds a slice of every VM.

Who leads your VM recovery
Executive Data Engineer / Executive Forensic Consultant
Viktor runs the Brisbane laboratory and leads every virtual machine and server case from the first call: he scopes the host and its storage with you, sets the imaging order for the disks and reviews each rebuild before anything is extracted. When a matter needs evidence handling, he signs the forensic report.
Datastore and snapshot chain reconstruction from disk images, ransomware cases where the disks must be preserved as evidence, encrypted volumes opened with the client’s own keys, and evidence-grade imaging with hashing and documented chain of custody for matters that may reach an insurer, a solicitor or a court.
The 20-second answer
It depends on which layer failed and on what has been written to the storage since. Recovery works from the bottom up: image every disk, rebuild the RAID or LUN, read the datastore, then rebuild each VM. The steps that most often make it worse are the ones that write to the storage: consolidating, rebuilding or running repair tools.
No consolidation, rebuild, reformat or restore onto the same storage. Pause the backup jobs that create and delete snapshots.
Every member disk is copied sector by sector before anything else happens, failed disks included. All further work is done on the copies.
The free assessment tells you what failed and what the recovery involves. Nothing chargeable starts until you approve the written quote.
How it works
To its users a VM is just a server. To the host it is a folder of files, stored on a datastore that every VM shares.
Windows sees an ordinary C: drive. It has no idea the drive is a file.
Shared by every VM on the host and spread across every disk.
01 Symptoms · start here
Choose the symptom closest to what you have seen. Your selection opens guidance for that fault and carries into the enquiry further down the page. Choosing the hypervisor first makes the guidance specific to how it stores your VMs.
The datastore is missing or inaccessible, the RAID or SAN under the host has failed or is degraded, or disks have dropped out. Every VM on that storage is affected at once, and every write or rebuild attempt changes what can still be read.
Do not rebuild, re-initialise or reformat anything to bring the datastore back, and do not swap disks between bays.
The storage is healthy, but one VM has a problem: a failed snapshot consolidation, a VM that started with old data, a deleted VM or virtual disk, a Hyper-V checkpoint that will not merge, or damaged files inside the guest.
Do not retry consolidation, delete snapshot files or point the VM at its base disk to get it running again.
Not one of those two? Choose the closest symptom below.
Choose what you see when you manage the VMs. You do not need the host running, or administrator access, to begin an enquiry.
The hypervisor, its version and the storage underneath are the most useful details.
How each platform stores VMs →Your platform
Tap the setup closest to yours. It sets the hypervisor and the storage; then choose the symptom below.
How each platform stores VMs →Choose a symptom to see your next step.
What goes wrong
One of the most common VM failures starts with a backup job that does not clean up after itself.
The VM starts again with data from night 1.
12 weeks of changes lostThe snapshot stays on disk and is merged on the copies.
Changes keptBefore you try anything
The aim is simple: leave the laboratory storage that can still be read as it was when it failed.
From the Wildfire lab
What we are seeing on business systems right now, written up so you can plan before something fails.
02 Costs · Quoted after assessment
Virtual machine recovery is quoted in writing after a free assessment, before any chargeable work. These are the things that decide the price.
Healthy disks image quickly; damaged ones need laboratory work first.
A lost configuration has to be worked out from the data.
Storage spread over several hosts is more work than one local RAID.
Thick or thin, how many snapshots, and any broken links.
Whole bootable VMs, single disks, or specific files and databases.
Encrypted VMs, BitLocker guests or ransomware. The keys you hold matter.
Priority handling is agreed and priced in the quote.
Hashed imaging and chain of custody, quoted separately.
Free assessment. Written quote. Your decision.
The assessment establishes what failed and what the recovery involves. Nothing chargeable starts until you approve the written scope and fees. Request my free assessment →
Before you decide
It depends on what the VMs hold and what else you have. These are the usual answers.
Usually worth an assessment: it is free and shows what can be read before you spend anything.
Restore and check it first. If weeks are missing, recovery can target just those VMs.
Ask about priority handling. The VMs you need most can come back first.
03 Process · Inside the lab
The work runs from the bottom of the storage up. Each step is checked before the next begins, and nothing chargeable starts without your written approval.
0102030404 Laboratory
Three engineers, one Brisbane laboratory, no account managers in between. The person who assesses your disks is the person who works on them and the person you can ring back.

Executive Data Engineer / Executive Forensic Consultant
Leads every virtual machine and server case and signs the forensic reports when a matter needs evidence handling.
Datastore and snapshot chain reconstruction, ransomware cases where the disks are preserved as evidence, and evidence-grade imaging with hashing and documented chain of custody.

Electrical Engineer
On VM and server jobs he handles the hardware under the datastore: failed disks, controller faults and power damage.
Member disks that will not spin up or identify, ROM transfers so a donor board addresses the right platters, and multi-disk array reconstruction when the controller has lost the geometry, so the datastore can be read from the images.

Co-founder · Mobile & Encryption
Co-founded Wildfire in 2018. On VM jobs he opens the encrypted volumes found inside recovered virtual disks.
BitLocker volumes inside Windows guests opened with the client’s recovery keys, encrypted phones and tablets, and the honest conversations about what an encrypted device can and cannot give up without its key.
“Excellent Data Recovery and re set up. Viktor goes above and beyond to explain everything regardless of how long it takes. After disasters through the years gone by with other so-called experts, it was stessfree and a relief to discover Wildfire. Excellent pricing and communication.”
“I hit the worst-case scenario with BitLocker locking me out completely a problem that could’ve cost thousands. Viktor stepped in and had it fixed in mere minutes. He didn’t just fix it; he guided me step-by-step exactly what to do.”
Choosing a laboratory for a VM outage
It should be yes, every time. Working on the original disks risks the only copy.
Ask by name: VMFS, ReFS, ZFS, LVM-thin, Ceph or vSAN.
At Wildfire it is one of the three engineers above, in Brisbane. Nothing is sent offshore.
After ransomware or a dispute, ask for hashed imaging and chain of custody.
05 Start
Describe what you have seen and the VMs you need most. Your selections from this page are carried into the enquiry for you to check.
Written scope and fees before recovery.
The assessment is free. Submitting this enquiry does not authorise chargeable recovery work.
Systems down right now?
1300 806 55706 Delivery
The VMs are rebuilt from all the disks together, so the order they sat in matters. Request your free Express post-in label first.
Every disk from the array, failed ones included, each labelled with its bay number. Not just the bad ones.
Anti-static bag, wrapped on its own, in a rigid box with 5 cm of cushioning all round.
Your contact details, the hypervisor, the RAID level if known and the VMs that matter most. Never a password or key.
Seal the box, attach the supplied label and keep the tracking details.
Call 1300 806 557 before packing anything, so the right disks are sent in the right order. Do not power-cycle, reseat or reorder disks.
Never pack logins or keys with the disks or put them in the enquiry. The laboratory arranges a secure way to receive them. Encrypted-drive recovery →
Tell us before intake. Chain of custody and evidence-grade imaging are scoped and quoted separately. Discuss digital forensics →
Tick the checks as you prepare the parcel.
07 Answers
Open a question for a direct answer. What can be recovered depends on the hypervisor, the storage underneath and what has happened to it since the failure.
Recovering virtual machines, virtual disks or the files inside them from a VMware ESXi or vSphere environment when VMware’s own tools cannot: the datastore will not mount, a snapshot chain is broken, a VM was deleted, or the RAID or SAN underneath has failed. VMware Technical Support does not recover lost data itself; its knowledge base refers customers to data recovery companies. The work starts with images of the disks, never with repairs on the original storage. The storage layers under a VM →
It is quoted in writing after a free assessment, before any chargeable work. The price depends on how many disks there are and their condition, the RAID or LUN layout, the datastore type, the state of each VM’s snapshot chain, what you need back, any encryption, how urgently you need it and whether evidence handling is required. What decides the cost →
The assessment is usually completed within a few business days of the disks arriving, and urgent cases can be prioritised. After that, the time depends mostly on how many disks there are, how large they are and their condition, because each one is imaged in full before the rebuild. The written quote gives the proposed timing.
Yes, in most cases the host itself is not needed. The VMs are read from images of the disks on our own equipment, so a host that will not start, or has been reinstalled, does not stop the recovery. Some storage depends on its controller, enclosure or encryption keys; call first and we will say exactly what to send.
The host can no longer read the volume the datastore lives on. The usual causes sit underneath VMware: a RAID that dropped a disk or lost its configuration, a SAN LUN that is no longer presented, or a path or driver change after an update. Less often the VMFS metadata itself is damaged. Creating a new datastore on the device erases the old one, so find the failed layer first.
A snapshot delete or consolidation did not finish, so the VM is still running on delta files that should have been merged into its base disk. Retrying can work when the storage is healthy and has space. When it keeps failing, the chain usually has a missing, locked or damaged link, and forcing it can merge the wrong data. How snapshot chains break →
Deleting a snapshot in Snapshot Manager does not delete your data: it merges the changes held in that snapshot’s delta file into the disk above it. On a healthy chain this is routine. On a broken chain or a full datastore the merge can fail part-way. Deleting the delta file itself from the datastore is different: that throws away every change made since the snapshot.
Usually the file is the starting point, not the problem. A virtual disk holds its own partitions and file system, so once it can be read, its files, databases and mailboxes can be extracted. When the VMDK or VHDX is itself damaged, deleted or part of a broken chain, it is rebuilt from the datastore first.
No. We do not connect to your host or run recovery tools over a remote session. The disks come to our Brisbane laboratory from anywhere in Australia, because many VM failures start with a physical fault in a drive or controller, and every disk has to be imaged on our own equipment before anything else is tried. Working only on those images also means nothing is written to your original storage. How to send the disks →
Only if every VM on it is also in a backup you have tested. A rebuild reads every remaining disk end to end under full load, and if another disk is weak, that is when it fails. If the VMs matter and there is no tested backup, have the disks imaged first and rebuild afterwards. RAID data recovery →
Only on a copy, and only when the storage underneath is healthy. Copy the whole VM folder to other storage and run the tool against the copy. Never run repair or recovery software against the only copy, on the datastore itself, or on a host whose disks are failing: software cannot fix a hardware fault, and every attempt reads or writes the failing storage again.
Stop writing to that datastore straight away: no new VMs, clones or restores onto it. A deleted VM’s files can often be found again from the datastore’s metadata and blocks while they have not been reused, but every write, and automatic space reclamation on thin or SSD storage, reduces what is left. Thin provisioning and deleted disks →
Not necessarily. This usually means the VM was attached to its base disk and skipped the snapshot files that held the newer changes. If those files are still in the VM’s folder and intact, the chain can be rebuilt on copies. Shut the VM down and do not delete anything in its folder. How snapshot chains break →
Sometimes. It depends on how much of each virtual disk was encrypted. Some attacks encrypt only the VM configuration files, or only parts of each large disk, and the rest can then be read from images. We cannot decrypt files encrypted with an attacker’s key. Isolate the hosts, keep every disk as it is, report the attack at cyber.gov.au and call before restoring anything. Ransomware on a hypervisor →
Yes. We work with VMware ESXi and vSphere, Microsoft Hyper-V, Proxmox VE and KVM, vSAN, Ceph, Nutanix, XCP-ng and other hypervisors. Each stores VMs differently, so tell us the platform and version in the enquiry. How each platform stores VMs →
Yes. Once the virtual disk can be read, its guest file system is treated like any other drive, so single folders, SQL Server databases, Exchange mailboxes or accounting files can be extracted without bringing the whole VM back. Tell us what matters most in the enquiry.
Yes. Your IT provider can make the enquiry, join the scoping call and receive the technical findings. Anything chargeable still needs your written approval of the quote.
Yes. VM and server cases can be handled with chain of custody and evidence-grade imaging: the disks are imaged read-only, hashed and documented, and recovered material is reported separately from what was simply located. Tell us before intake, because the scope and fees are agreed in advance. Digital forensics →
Your data stays in Australia, on our own equipment in the Brisbane laboratory. Nothing is sent offshore or stored in a third-party cloud as part of the recovery. Working copies are destroyed after the verification window, or earlier on request with a certificate of destruction.
08 Learn
How snapshot chains break, why full datastores pause VMs, what ransomware does to a hypervisor, and where each platform keeps your VMs.
Snapshots and checkpoints
A snapshot freezes a virtual disk and sends every new write to a delta disk that depends on it. Each later snapshot adds another link. The VM can only be read through every link in order, from the base disk to the newest delta.
Space
Thin disks take space only as data is written, so a datastore can promise its VMs more space than it has. Snapshots grow the same way. When the space runs out, the VMs that need to write are paused with a no-space message until space is freed.
The whole disk is allocated when it is created, usually in one piece. A deleted thick disk is often easier to find again, because its blocks sit together.
Blocks are allocated as data arrives, so a thin disk is often scattered across the datastore. Recovering a deleted thin disk can mean rebuilding it from its blocks.
Ransomware
Attacks on ESXi and other hypervisors encrypt the VM files on the datastore, so every server on the host stops at once. They do not always encrypt everything: in the 2023 ESXiArgs attacks, the US Cybersecurity and Infrastructure Security Agency reported that the configuration files were encrypted while the flat disk files could be used to rebuild the VMs.
Disconnect the affected hosts and storage from the network. Power down only if they cannot be isolated, because evidence held in memory is lost at power-off.
Keep every disk as it is, with the ransom notes and renamed files. Do not wipe, reinstall or restore over the storage. The disks are imaged first, with chain of custody if the matter may reach an insurer or a court.
Report the attack to the Australian Signals Directorate through ReportCyber at cyber.gov.au. If personal information is involved, the Notifiable Data Breaches scheme run by the OAIC may apply. Payment reporting and breach deadlines: ransomware data recovery.
Where the VMs live
The type of datastore decides where recovery starts and which disks have to be sent.
Block storage formatted by VMware. Recovery starts with the disks of the RAID or the SAN, then reads VMFS from the rebuilt volume.
The VM files sit in an ordinary folder on the NAS’s own file system. Recovery is a NAS recovery first: the NAS disks are imaged and its volume rebuilt, then the VM folders are read from it.
Hyper-V keeps its .vhdx files on Windows volumes, often a Cluster Shared Volume on a SAN that several hosts share.
Each VM’s data is spread across the disks of several hosts. Every host and disk is identified together before anything is removed.
Proxmox VE
On Proxmox, a VM’s settings and its disks live in different places, and both are needed to bring it back as it was.
Each VM’s configuration is a small text file under /etc/pve/qemu-server/, named after the VM’s number. /etc/pve is not an ordinary folder: it is the Proxmox cluster file system, stored in a database at /var/lib/pve-cluster/config.db on every node.
qcow2 or raw files on directory storage, volumes in a ZFS pool, thin volumes in an LVM-thin pool, or images in Ceph. These are recovered from images of the disks underneath.
Sources
Sources checked 6 November 2026. Hypervisor messages in the library below each link to the vendor page that documents them.
09 Library
Search a hypervisor message, a platform or a term. Every message is quoted as the vendor documents it, with a link to that page. Message records can carry the symptom into your enquiry, and platform records can set the hypervisor for your recovery path.
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
Source checked 6 November 2026 · Bookmark this record
VMware’s name for the storage that holds VM files: a VMFS volume on a disk, a RAID or a SAN LUN, or an NFS share. One datastore usually holds many VMs, so one failure can stop them all.
Source checked 6 November 2026 · Bookmark this record
VMware’s cluster file system for datastores on block storage. Several ESXi hosts can share one VMFS volume on a SAN. VMFS 6 is the current version.
Source checked 6 November 2026 · Bookmark this record
A VMware virtual disk. On VMFS it is two files: a small text descriptor (.vmdk) and the data file (-flat.vmdk). Snapshots add delta disks that depend on it.
Source checked 6 November 2026 · Bookmark this record
A snapshot preserves a VM’s state at a point in time. After it is taken, writes go to a new delta disk and the disk below stops changing. A snapshot is not a backup: it depends on every disk below it in the chain.
Source checked 6 November 2026 · Bookmark this record
Merging snapshot delta disks back into the disk below, so the VM runs on one disk again. vSphere flags a VM when consolidation is needed after a snapshot delete did not finish.
Source checked 6 November 2026 · Bookmark this record
A virtual disk that takes datastore space only as data is written, so a datastore can promise its VMs more space than it has. A thick disk reserves all of its space when it is created.
Source checked 6 November 2026 · Bookmark this record
Tells thin-provisioned storage which blocks the file system no longer uses, so the storage can reuse them. On VMFS 6 it can run automatically. Blocks that have been reclaimed may no longer hold the deleted data.
Source checked 6 November 2026 · Bookmark this record
Hyper-V’s virtual disk format (.vhdx) and the differencing disk created for each checkpoint (.avhdx). A differencing disk records changes and depends on its parent.
Source checked 6 November 2026 · Bookmark this record
A Windows failover cluster volume that several Hyper-V hosts read and write at the same time, usually on a SAN. VMs on a CSV are recovered from the shared storage, not from one host.
Source checked 6 November 2026 · Bookmark this record
QEMU’s copy-on-write disk image format, used by KVM and Proxmox. It supports thin allocation, internal snapshots and backing files, so one image can depend on another.
Source checked 6 November 2026 · Bookmark this record
ZFS combines disks into a pool and stores VM volumes inside it. A forced import in recovery mode (zpool import -F) returns the pool to an importable state by discarding the last few transactions, which is why it is never run on the original disks first.
Source checked 6 November 2026 · Bookmark this record
A Linux thin pool that Proxmox can use to hold VM disks as thin volumes. Like other thin storage, it can promise its volumes more space than it has.
Source checked 6 November 2026 · Bookmark this record
A sector-by-sector copy of a whole disk, made before any repair or rebuild. All further work is done on the images, so the original disk is not changed.
Source checked 6 November 2026 · Bookmark this record
The documented record of who handled the disks and images, when and how, with hash values showing the copies have not changed. It matters when the data may be evidence.
Source checked 6 November 2026 · Bookmark this record
Disks striped with rotating parity, so the array survives the loss of one disk. While degraded it has no protection left, and a rebuild reads every remaining disk in full.
Source checked 6 November 2026 · Bookmark this record
Ready when you are
Free assessment of every disk. Written scope and fees before any chargeable recovery work.