A virtual machine may lose its existence due to reasons a physical machine cannot: an accidental deletion of or overwrite on the VMDK or VHDX file for the virtual machine, corrupted snapshots, loss of the entire datastore resulting from failure of the underlying storage or inability to start the VM as a result of a host system crash. Usually there are very large, complete virtual disks underneath. Most often these disks can be restored. We recover VMware, Hyper-V and other virtual computers, from the datastore up. Whether you searched VMware recovery, VMDK recovery or Hyper-V recovery, the diagnosis is free and in most cases you only pay if we recover your data.
Do not create a new VM; do not consolidate your snapshots; do not recreate the datastore: this is typically what overwrites a deleted or corrupted virtual disk. Put the host offline so we can image the storage.
Virtual machine loss occurs in one of two ways. Above the datastore: a VMDK or VHDX has been deleted/overwritten, a snapshot chain is broken/inconsistent, or the descriptor is pointing to the wrong delta. Below the datastore (on the physical disks/RAID array/SAN): all VMs on that datastore are lost if the physical disks fail. A host crash can leave the VMs running on it unable to boot, yet each VM may have an intact disk. Each of these needs a different route, and re-creating the datastore or consolidating snapshots blindly is how recoverable virtual disks get overwritten.
If the storage fails completely, we begin by rebuilding the array or datastore underneath that failed (just like we would with a RAID or SAN failure) to get a usable copy of your original data. Once we have a valid copy of your data, we can now pull out the VMDK (virtual disk) images from the datastore. If the datastore is good but either the VMDK itself or a snapshot chain of VMDKs is bad, we will create a new copy of all the virtual disks from their base and delta files; fix up the snapshot chain; and restore the file system of each individual guest operating system. In both cases, we end up with a mountable copy of the original virtual disk(s) and/or we provide you with all of your files from within them, rebuilt from copies so the originals are never touched.
We can restore virtual machines from VMware ESXi and vSphere (VMDK and VMFS) as well as Microsoft Hyper-V (VHD/VHDX). We also support recovery from Proxmox, VirtualBox, and KVM. All virtual machine recovery is based upon recovery from either local storage, RAID arrays, NAS, or SAN systems. If recovering from a host server or RAID array, please take the disks out of the server or enclosure and ship us all of the disks that hold your virtualisation environment. Additionally, be sure to let us know what VMs you want recovered, as well as the exact point in the snapshot chain you would like them restored to.
Yes, most often, but only if no one has overwritten the area where the deleted virtual disk was stored. Deleted virtual disks usually remain in the datastore until they are overwritten with new data. Therefore it is best to remove the host from production as soon as possible and allow us to create an image of the datastore. The quicker you stop using this area on the host, the greater will be our chances of successful recovery.
Yes; however, extracting virtual machines from a recovered datastore (after rebuilding your failed array/SAN) requires two parts: imaging and recovery of the datastore. Please take the disks used for storing the original datastore out of the server or enclosure, then package them in their original order and send them to us.
First, we build the restored virtual disk image from the base and delta files. Then, we reconcile the different descriptors of the disk’s contents, and finally extract all the data that was in the guest operating system (files, documents, email etc.) from this reconstructed disk. Do not try to perform a blind consolidation first. A consolidation will write over the deltas you are trying to restore.
Yes. Once we have built our virtual disk image and mounted the guest file system, we can recover your specific files, databases or mailboxes etc. exactly as if they were on an actual physical hard drive.
Often, yes. First, we image the storage that contains the guest OS; next, we recover/repair the VMDK/VHDX container to which the guest OS belongs; lastly, we rebuild the guest file system within this container. Three levels of work, always performed on copies of each level. Snapshot chains do make recovery somewhat more difficult, so stop any further consolidation and, once you have a quote, send it in as it is.
We provide a complimentary diagnostics check for every client, plus an accurate, and completely fixed, quotation to do that job, prior to starting any work on a job, and we don’t ask for payment on most jobs unless there’s enough recoverable data. Quotations for VM recoveries are provided once the diagnostic has been completed (as many times these require a rebuild of the base level of storage first), but will be supplied in writing prior to any costs being incurred. Once you have received a quotation, just bring your device down to our Leeds location within The Pinnacle (you don’t need an appointment) or send it via fully insured postal delivery from anywhere in Yorkshire. In either case, your device is processed internally by our own engineers with no sub-contracting.
Searching virtual machine data recovery near me usually means a corrupt or deleted VMDK/VHDX file, or one on a dead datastore. VM recovery is layered: the storage underneath, the container itself, then the file system inside it.
Once you have received a price quotation from us, you may either leave your device at The Pinnacle, Albion Street in the city centre (no appointment is required) or you can send it to us insured and tracked as part of our data recovery UK-wide service, with the same free diagnostics as well as the same fixed written quote, and in most cases, you do not need to make payment unless we successfully recover your lost data. Each project will be completed by one of our own engineers.
The diagnosis is free. The quote is fixed in writing. Most jobs carry no fee unless your data comes back. Do not re-create the datastore. Do not consolidate snapshots. Take the host offline. Once you have a quote for your project, send the storage to us (for a server, remove the disks from it).