VMware Recovery
VMware failures sit across several layers — datastore, virtual disk and guest file system. AS recovers at each layer from images of the underlying storage.
When you need this
- VMFS datastore inaccessible or shows as unformatted
- VMDK deleted, corrupted or snapshot chain broken
- ESXi host failed and VMs cannot be re-registered
- Storage failure beneath the datastore
- Ransomware targeting ESXi hosts and datastores
- Thin-provisioned VMDK corruption
What we do
Datastore recovery
VMFS 5 and 6 structures are reconstructed to locate virtual disks, including deleted VMDKs where their extents survive.
Virtual disk repair
Damaged descriptors, flat files and snapshot chains are repaired or reassembled.
Guest-level recovery
Files, databases and mail stores are recovered from within virtual disks when a whole-VM restore isn't possible.
Hypervisor ransomware cases
Encrypted ESXi environments are assessed for recoverable datastore and VMDK content where technically feasible.
How it works
- Step 1
Consultation and scope
We establish what failed, what has been tried, and which data matters most. This shapes a targeted plan rather than a generic one.
- Step 2
Secure imaging and diagnosis
Where possible the source media is imaged before any work, so the original is never altered. Diagnosis then determines the safest recovery method.
- Step 3
Recovery
Data is extracted from the image or source using methods matched to the failure — logical, structural or hardware-level as required.
- Step 4
Verification
Recovered data is checked for integrity and completeness, and a file list is shared so you can confirm what matters is there.
- Step 5
Secure delivery
Verified data is returned through an agreed secure method, with guidance on validation before it goes back into production.
What affects the outcome
Outcomes are never guaranteed. Every case is assessed on its own condition, and we tell you what is realistic before you commit.
- Physical condition of the media and the extent of any damage
- Whether the media has been written to, reformatted or re-initialised since the failure
- Encryption, corruption or partial overwriting of the data
- Availability of source data such as images, backups, logs or transaction records
- Attempts made before assessment (rebuilds, repair tools, repeated reboots)
AS VMware Recovery
Recover VMDK and VMFS data on your own hardware for logical failures on readable storage.
Frequently asked questions
A VMDK was deleted from the datastore. Can it be recovered?
Frequently, if the datastore has not been heavily written to since. The sooner the datastore is taken out of use, the better.
Do you need the ESXi host?
No. Recovery works from the storage beneath the datastore, imaged independently.
Related services
Not sure what you're dealing with?
Describe the situation and we'll tell you what's realistic.