A trusted VMware® partner

We partner with VMware to increase success on all VMware data recovery projects. Do you have the latest version of VMware and need data recovery? Our engineering team works closely with VMware in order to create successful tools for all VMware data recoveries.

Data recovery for all virtualization

Ontrack Data Recovery are the experts in data recovery and can perform successful data recoveries from nearly any virtual machine, server or system; including:

Virtual infrastructure: VMware®, Microsoft® Hyper-V®, Citrix® and Linux® XEN®, Oracle® VM

Virtual file systems: VMFS, NTFS, FAT, EXT3, HFS, etc.

For a complete list of recoverable systems and file types, contact us at +9714275 7433.

The most common data loss situations in virtual systems

  • Re-formatted VMware 'Datastore'
  • Corrupted virtual disk files (VMDK)
  • Corrupt VMFS Datastore volumes
  • Deleted virtual disk files (VMDK)
  • Corrupted file systems
  • Traditional RAID and hardware failures

Tips for common scenarios for VMware data recovery

If you suspect data loss the first requirement is to record any information you know about the missing or deleted virtual disk. Relevant data includes: virtual disk size, thick or thin provisioning, virtual machine name, guest file system and the type of data contained. Next, reduce reads and writes to the affected datastore. If the datastore contains active, thin provisioned virtual machines, power them down as soon as possible. Whatever you do, don't migrate any active virtual machine (Storage vMotion or otherwise) to or from the affected datastore without first speaking to a data recovery professional. You may unwittingly increase the complexity of the VMware data recovery and could reduce the chances of retrieving the data. In case of a VM with missing or deleted snapshots, don't power it on. And if the machine is currently running, power it down as soon as possible.

To minimize problems, never attempt to recreate the datastore and if you are investigating the LUN yourself, ensure that read only access is used.

Never replace a failed drive with a drive that was part of a previous RAID system; always zero out the replacement drive before using it. If the drive is making unusual mechanical noises, turn it off immediately and get assistance. Just as in the physical server environment, leaving a mechanically failing drive powered on increases the likelihood of further damage and significantly reduces the chances of a full recovery. Tip: Label the drives with their position in a RAID array before removing them from your system. If a RAID system fails in the middle of a rebuild process, do not run further rebuild attempts. Never migrate VMs to or from a suspect RAID, and if you do need to shut down or power cycle your RAID hardware, ensure all virtual machines and VMware hosts are gracefully shut down first.

Don't try to run volume repair utilities (such as CHKDSK) or defragmenter utilities on suspected corrupt virtual disks as this can exacerbate problems. If you find that more than one virtual machine shows signs of corruption, you may have a problem at the storage level. Power down the machines and consult a VMware data recovery professional as soon as possible.

Microsoft Hyper-V Data Recovery

Hyper-V enables easy creation and configuration of VMs in order to set up an environment that is fully suited to your virtualization needs.
Microsoft Hyper-V, like all other virtualization environments, can be subject to data loss.
The most common causes are:

  • Human error
  • NTFS corruption
  • Corrupted or deleted files in VHD
  • Hardware or RAID systems’ breakdown or malfunction

Ontrack supports the following Microsoft virtualization platforms:

  • Microsoft Hyper-V
  • Microsoft Virtual Server
  • Microsoft Virtual PC

Frequent data loss scenarios in Microsoft Hyper-V

The R&D Team at Ontrack has created a dedicated toolkit for Hyper-V data recovery, enabling our engineers to recover data even in the most complex environments.
We can assist you with all data loss scenarios, such as:

  • Corrupted NTFS volumes
  • Corrupted VHD
  • Deleted VHD
  • Deleted VMs
  • Hardware or RAID systems breakdown or malfunction
  • Accidental data erasure
  • Corrupted or deleted snapshots