Windows Server 2019 not booting after restore to Proxmox via Veeam

[ab47]

First time posting here and relative newbie using Proxmox. Don't roast me too much. Trying to restore a 2019 windows server, from Veeam B&R 12 to Proxmox 8.2.7. The server was working perfectly before the restore. This is what is showing from the console.



Then it goes into windows recovery.

Here's the details of the hardware.



Here is a log when starting the vm:




Any ideas on why my server isn't starting correctly? TIA.

 

[carles89]

Maybe you're hitting this bug: https://forum.proxmox.com/threads/veeam-silent-data-corruption.155212/post-718208, have you tried with the last version of PVE plugin for Veeam?

 

[ab47]

Downloaded and installed the new plugin. Tried to restore and same issue. This isn't good as it's a production server for new software in our Quality department.

 

[Blueloop]

Random thoughts - I'm still finding my feet around here too somewhat:

• You are using EFI and probably TPM and Secure Boot. Should the machine type be i440? Try q35.
• Detach the hard disc. Add it back as a SATA. Switch the boot to BIOS instead of EFI. Don't worry, the disc file remains the same regardless of the interface and boot type. If that fails, try IDE (no, I am not joking)

Once you get it working, fix each issue one at a time. Almost certainly, booting the disc as SATA will get you up and running (unless the data on it is rubbish)

 

[ab47]

@Blueloop, i don't have the option to add the hard disc back to the vm??? I only have the option to create a new HDD.

 

[ab47]

Restored another production VM and that was restored without any issue. Something with the backup type from Veeam that was the culprit. Thank you for your help and time. i appreciate it. Anthony

 

[Blueloop]

After you detach the disc, it drops to the bottom of the hardware list. Double click on it and you can re-attach it to a different bus type.

Glad you sorted it out.

I seriously recommend creating a few sacrificial lamb VMs to play with various scenarios, when time permits. On Windows, try installing as BIOS boot and converting to EFI with Secure Boot. For a giggle, move the EFI partition around.

Use a snapshot beforehand that you can roll back from.