Backup failed:GUID must contain 32 digits with 4 hyphens

[mros]

Dear community,
i am having problems backing up a virtual machine with Windows Server 2022 and Proxmox VE 8.2-2.

The backup of an ESET Protect VirtualAppliance works. I changed the hardware version of the Windows Server 2022 VM yesterday November 18th from machine type Q35 version 8.1. to Q35 version 8.0 without success. The following message is displayed:
DC : GUID must contain 32 digits with 4 hyphens (xxxxxxxx-xxxx-xxxx-xxxxxx-xxxxxxxxxxxxxx); Job finished with error at 11/18/2024 8:36:29 PM

If i query the GUID from within the VM via powershell it gives me the following result:
get-wmiobject win32_computersystemproduct | Select-Object -expandProperty UUID
32XXXXXX-3XXX-4XXX-8XXX-80XXXXXXXXXX

I had to use custom SMBIOS Settings to activate the ROK licence from microsoft. So the GUID comes from the HP Server ProLiant ML350 Gen11
Did someone have an advice to resolve this issue ?

The Case ID which i created yesterday 19.11.2024 is #07508744

Regards
Mike

[PTide]

Hi,

I have requested an escalation for this one. Stay tuned.

Thanks!

[mros]

Hi, thanks for your reply. I added the information of veeam B+R and the Proxmox PVE Plugin.

Veeam Backup & Replication 12.2.0.334
Proxmox Virtual Environment Plugin for Veeam Backup & Replication 12.1.0.313

[mros]

A brief update from my side. I installed an additional VM with the Windows Server 2022 Standard ISO (Server_STD_2022_2108.14_X23-25645_10-2022) last week and the backup works flawlessly on the VM. I then took the Windows Server 2022 ROK again and installed another VM with it. The error “GUID must contain 32 digits with 4 hyphens” is also triggered here. It looks like it is due to the Windows Server 2022 ROK image.

Best regards

[MoritzG-Seidemann]

Also using a HPE ROK ISO 2022 with the STD and DC editions. Do you know a way to get a newer ISO version? Seems like ripping a CD is the only resolution to get one.

[mros]

Hi, i don't know where do i get a newer version of this DVD. According to this site: https://www.hpe.com/psnow/doc/4aa4-3787enw which contains a pdf with further information. There is another site where is it possible to order a replacement for defective media: https://ebiz3.mentormediacorp.com/HPEDGRCR

I will try to open a support case at HPE, since they are giving an initial installation support for 90 days after purchase which covers january-february 2025

[mros]

Short update, the support closed my case so opened a new one with the same issue
Case #07581440

[MoritzG-Seidemann]

Thanks for keeping us updated

[marcquark]

just wanted to report that i'm facing the same issue, seems to affect VMs where SMBIOS settings are customized. in one instance i had to put something into the "Serial Number" field, in another instance i had to specify a manufacturer. both VMs aren't getting backed up

[MoritzG-Seidemann]

Interesting. I believe my VM only has a manufacturer set (because I used a ROK license) but no model or I edited out at a later date).
I will try including some data and see if it works.

[MoritzG-Seidemann]

I checked yesterday the system options in the SMBIOS settings.
After adding my VM as a backup item it failed (as expected). The only items with content were the BIOS-UUID and the manufacturer ("Hewlett Packard Enterprise")

I emptied the manufacturer string, backed up again but it failed with the information that it couldnt find the VM.
After re-adding the VM in the job (refreshing the host info) I restarted the job and it successfully backed it up. Restore also worked (To the Veeam Dev Team: Job well done)

[rovshan.pashayev]

Hi All,

FYI: In the latest build release, this issue has been solved