Hi ​@hs08,

I guess you are using either ESXi 7 or ESXi 8 and as far as I know both systems with the appropriate VM versions can use EFI with BIOS compatibility. You should be good selecting EFI even if the OS disk in backup uses MBR.

With Veeam warnings often indicate things but do not necessarily lead into errors so I recommend to use EFI and try to run all steps of the recovery wizard.

A few questions to unterstand the whole situation:

• Which ESXi version are you using?
• Which Veeam Agent version are you using?
• Which OS does the system you are trying to restore use?

Take care!

Lukas

Selecting EFI with BIOS compatiblity should do the job !

Hi ​@hs08 -

Have you seen Veeam’s KBs on these errors?

https://www.veeam.com/kb3156

https://www.veeam.com/kb2407

Best.

Hi ​@lukas.k 

• Which ESXi version are you using? Version 7
• Which Veeam Agent version are you using? Version 6.3
• Which OS does the system you are trying to restore use? Windows 2019

Hi ​@kristofpoppe , ​@coolsport00 

I already read the article but my question is if we set to EFI then Veeam Agent say ‘OS disk in backup uses MBR disk’. If i change to BIOS then the Veeam Agent say ‘OS disk in backup use GPT disk’.

So why the Veeam agent is not consistent when give the warning and make me confuse.

If the OS disk in backup use MBR, then i change the firmware to BIOS then the warning should be gone and not should not saying OS disk in backup use GPT because this make me confuse.

Hi ​@hs08 -

If you tried the steps in both KBs, I don’t really have much more to add. We can only try to help here in the Community. It’s rare someone here would know why the behavior of Veeam’s product does what it does at times. For those questions, you should ping Veeam Support. Sometimes a Community member is from Veeam and may comment. But even so, they always recommend to contact Support to help resolve issues you’re experiencing.

If you do reach out to Support, keep us posted what they say.

Best.

Hi ​@coolsport00 

Since i use veeam agent free edition, i’m not able to open the ticket.

I was trying change from BIOS to EFI then the restored OS can’ be boot up.

Lastly i try to not recover the small partition (disk31) and after restoration is finished, the restores OS can boot up normally.

When checked to the source server, i also can’t see this 4MB disk on the disk management source server.

This might be a hidden partition on the source disk or the source system.

Good to hear that it works now. 

You should make sure to do all required after work on the restored system: cleanup drivers, remove “dead” devices, modify VMware tools if required and keep in mind that network adapters and configurations may change.

Hi ​@coolsport00 

Since i use veeam agent free edition, i’m not able to open the ticket.

I was trying change from BIOS to EFI then the restored OS can’ be boot up.

Lastly i try to not recover the small partition (disk31) and after restoration is finished, the restores OS can boot up normally.

When checked to the source server, i also can’t see this 4MB disk on the disk management source server.

 

 

Hi ​@hs08 -

You are able to submit a Support request for the free edition, as shown in the helpcenter VAW User Guide:
https://helpcenter.veeam.com/docs/agentforwindows/userguide/support.html?ver=60

Best.

​@hs08 do you want to restore into the VMware? why don’t you try to export the backup to um VMDK file and use it on your VM?

Hi ​@hs08, why making it so complex? You can restore an Agent Backup directly as a VM within VBR:

Restoring Veeam Agent Backup to vSphere VM - Veeam Agent for Microsoft Windows Guide

hi ​@AndrePulia , ​@Dynamic 

This i need for testing purpose, because i don’t have other baremetal server so i simulate restoration to vmware use recovery media.

HI ​@hs08 , I see. so you can create a VM and use it as it was a physical server, the process is exactly the same.