VMware recovery scenario's
Op basis van wereldwijd door Ontrack uitgevoerde VMware recoveries tips om verder verlies van gegevens op VMWare omgevingen te voorkomen (engels).
Deleted or Missing Virtual Machine/VMDK
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, VM 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 VM (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.
Corrupt VMFS Metadata or inaccessible Datastore
To minimise problems, never attempt to recreate the datastore and if you are investigating the LUN yourself, ensure that Read Only access is used.
Mechanical failures and RAID/Storage issues
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 VMs and VMware hosts are gracefully shut down first.
Corruption inside Guest OS
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 VM 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.