VMware and Hyper-V are more similar than people realize. Because backup vendors try to build a degree of consistency into their software, a simple virtual machine (VM) restoration might be performed identically for both a VMware restore and a Hyper-V restore when using a given backup application.
Hyper-V uses a relatively simple architecture for its VMs. Each VM has a configuration file and one or more virtual hard disks. There may also be files associated with checkpoints if they exist. These particular components can be stored on any supported storage. Hyper-V is extremely flexible with regard to the location of a virtual machine.
VMware maintains an inventory of objects, so performing a VMware restore can be a bit more involved. These objects have a hierarchical relationship to one another. If a dependency object no longer exists, it must be recovered or the VM must be linked to another object.
For example, VMware virtual machines exist within data stores. If a data store does not exist, it must be recovered prior to restoring a VM or in conjunction with restoring a virtual machine. Otherwise, the VM will have to be recovered to a different data store.
Backup and restore still important with VMware
Three methods for backing up, restoring VMware data
Pros and cons of traditional backup software vs. VM backup software
How to solve Hyper-V recovery problems