An infrastructure with 50 VMs has a power outage. After the VMware cluster has booted up again, 10 large VMs are orphaned. However, all VM disk files are still on the datastores. What is the quickest way to bring back those VMs with the least possible data loss?
To quickly bring back the orphaned VMs with the least possible data loss, the best approach is to perform a restore of only the VM configuration files. This method allows you to recreate the VMs in VMware vSphere using the existing disk files on the datastore without the need to copy or transfer large VM disk files. This is both efficient and effective, assuming the VM disk files are intact on the datastore.
By performing a restore of only the VM configuration files, you can quickly recreate the VM in VMware vSphere using the existing disk files on the datastore. This method avoids the need to transfer or copy large VM disk files, resulting in a faster restoration process. Note that this method assumes that the VM disk files are still intact on the datastore. If any of the VM disk files are missing or corrupted, you may need to consider alternative restoration methods or perform a full restore from the Veeam backup files.
A. Remove the existing VM disk files from the datastore and perform Instant VM Recovery.
With this option, you can use Instant VM Recovery to quickly start the VMs from their existing disk files without the need to copy or restore the data. Quick rollback allows you to revert any changes made during the recovery process, minimizing data loss. Automatic Power On VM at the end ensures that the VMs are powered on as part of the recovery process.
theoretically C, but I cannot imagine who will dare to actually do this :-D
C, teher is no quick rollback in Instant VM Recovery
It's C. You don't use quick rollback as a result of power outage. And you need only the VM config files, as the data in the vmdks is fine.
C is correct
Agree with Beber. Also: 1. There is no quick rollback option when using Instant VM recovery. 2. Quick rollback description in VBR console states: "Do not use this option when recovering from disaster caused by hardware or storage issue, or power loss."
Finally not sure with the least possible data loss? Could be option D