Skip to main content
  • EN

My recent discovery so it could help someone not to loose time. And maybe if there is a solution I’ll be most thankful.

So with Proxmox version 9 you need to set Machine type to version 9.2 instead of Default as it defaults to 10 and that causes Veeam backup to fail. 

 


That will insure that your backup will be sucesful and restore will work too.

 

I have issue, where I am migrating servers from Hyper-v to Proxmox and usual and most painless solution was to use Veeam Backup&Restore as intermediary as we are already using it.

But in this case restore to proxmox fails as when VM is created is created with default version for machine type and this defaults to 10 and this results in: Failed to prepare disks for restore. (If anybody knows how to convince the process to default to 9.2 Mychine type I’ll buy you a beer).

I tested this on 12.3 and on veeam appliance 13 with the same result. I can restore VM, that was originally backed from Proxmox as it will bring it’s machine type version along.

Hi ​@ToneK -

So...are you looking for a solution on how to perform a restore to Proxmox using the correct PXMX VM version? There doesn’t appear to be a setting in the restore wizard for doing so. As such, it would probably be best to go to the Forums and ping the Veeam Product Managers for a PXMX feature request to be able to choose/set a VM version during restore to hopefully resolve this error/failure and enable VMs to be powered on successfully; unless someone else chimes in here with a workaround.

Best.

Was just about to suggest what Shane did checking on the Forums as that would be a more technical place to search.  Hopefully someone has a workaround for this.

Are you not able to restore to Proxmox but before power on change the version?  Never used Proxmox so just asking.

Problem is, that if Machine type version is 10 then apparently disks that are added to VM are managed somewhat differently and then restore fails. 

 


When you restore to proxmox VM is created and when data should be copied to disks that fails, and when that happens VM is automatically deleted and you can’t do much about it.

If Machine Type version is wrong backup fails in similar fashion, regardless if it’s powered on or not. ​​​​​​

Ok then you need to open a support ticket and check the Forums for further solutions/workarounds.  Unfortunately the community is not a technical support forum. 😁

 
 
 

​@ToneK - yep...you’ll need to go to support on that one. We wouldn’t be able to help here.

Hi ​@ToneK, can you please open a support case, uploade your logs and post the case ID here? I'll take a look at the case and forward it to my colleagues afterwards. 

Hi ​@ToneK, can you please open a support case, uploade your logs and post the case ID here? I'll take a look at the case and forward it to my colleagues afterwards. 

Case #07854147 - I just completed the more detailed work of opening the case. 
 

My suspicion is that if VM is created and if environment was proxmox it will carry information of machine type and version with it. But when VM originates from another hypervisor that information is missing and worker creates VM with default machine type and version and that is sadly incorrect version so restore fails. 

Terms & ConditionsAccessibility statement