Skip to main content

VMCE Practice Question - 26 February 2025 (VTT)


coolsport00
Forum|alt.badge.img+20

Happy Wed everyone. Below is this week’s VTT question…

For those new to the VMCE page, please hide your comment (guess). To do so → before typing your response, click the ellipsis icon on the far right of the format toolbar at the top in your comment box and select the Spoiler option. This will place a ‘hide comment’ text box in your comment box area. Click inside this hide comment text box and start typing your answer (guess). Be careful to not click outside of the box or your comment will show after saving. We want your comment to not show so others can take full advantage of these practice questions. Let me know if you have issues. Good luck!

~~~~~~~~~~~~~~~~~~~~~~~

At 6:00pm, after an issue, a VM is stuck in: 
Error code 0x000000f The application or operating system couldn’t be loaded because a required file is missing or contains errors.
The VM is configured as shown in the table.  During troubleshooting, a VMware administrator found a datastore was not available several times. The last backup was created at 1:00am.
Choose the recovery approach providing the lowest RTO and the least amount of data loss.
VM Configuration
  1. Instant VM Recovery
  2. Instant Disk Recovery with Quick Rollback
  3. Instant VM Recovery with Quick Rollback
  4. Instant Disk Recovery

 

9 comments

  • New Here
  • 6 comments
  • February 26, 2025
Show content
  1. Instant Disk Recovery

You can’t use quick rollback because the data store was unavailable hence b and c are out. d remains correct. Since the VM has multiple disks, Instant Disk Recovery is the most suitable restore method

 


Dynamic
Forum|alt.badge.img+8
  • Influencer
  • 361 comments
  • February 26, 2025
Show content

A - Instant VM Recovery or

D - Instant Disk Recovery

As i don’t know if the VM has only problems within the OS (BSOD) on Disk 1 - imho the best solution should be A. If it’s sure, that only the OS Disk has problems, and the Data on Disk 2 is intact, D would also work.

 

I go with A

 

B & C shouldn’t be used, if the error was due to a failure within the Hardware/SAN environment. AS you mentioned, the Datastore was not available.

 

 

 

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8400 comments
  • February 26, 2025
Show content
  1. Instant Disk Recovery with Quick Rollback

 

 
 
 

Mohamed Ali
Forum|alt.badge.img+1
  • Experienced User
  • 35 comments
  • February 26, 2025
Show content
  1. Instant Disk Recovery with Quick Rollback with Disk 1 OS drive 

 


 

 


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 602 comments
  • February 26, 2025
Show content

​​​​A ​​​​​​) Instant VM Recovery 

 


DavideAbrigo
Forum|alt.badge.img+1
  • Experienced User
  • 116 comments
  • February 26, 2025
Show content

I would go with D. Instant Disk Recovery for disk 1 (OS)

 


MarcoLuvisi
Forum|alt.badge.img+5
  • Influencer
  • 265 comments
  • February 26, 2025
Show content
  1. Instant VM Recovery

If have storage issue I think is right way.

 


coolsport00
Forum|alt.badge.img+20
  • Author
  • Veeam Legend
  • 4109 comments
  • February 28, 2025

Ok everyone, below is the answer to this week’s VTT question. This one was good imo!

Show content

So, let’s first knock out 2 options right off the bat → b. and c. Why? Quick Rollback is not an option for any Instant VM operation beit VM or Disk. It is only a restore option for Entire VM or Disk, and when restoring to the original location. Also, you do not use Quick Rollback if there is a VM hardware or some other virtual infrastructure failure. So even if the options were for Entire VM or Disk, we wouldn’t use this feature because the question states there was a Datastore failure.


That leaves either a. or d. And the quickest restore would be to just restore the disk, not entire VM. So d. Instant Disk Recovery is the correct answer here. For more info, see URL below:

 

https://helpcenter.veeam.com/docs/backup/vsphere/instant_disk_recovery.html?ver=120

 


  • New Here
  • 1 comment
  • March 1, 2025
Show content

I would answer B: Instant Disk Recovery with Quick Rollback
Considering that indeed, there seems to have happened a HW incident (datastore disconnection), that seem to have been a temporal condition, however, that would explain why the VM got a corrupted system file in the first place, but since that condition is corrected (the scenario say that there were datastore disconnections and not that the datastore is currently unavailable), after the datastore is available, we can try an Instant disk recovery with quick roll back to get the best RTO.

 


Comment