Failed to convert [Not Settable] to UUID

[DavideC]

Good morning dear users,

I have recently installed Veeam Backup & Replication on a Windows Server 2022 virtual machine to back up some virtual machines on my Proxmox Hyper-V.
However, when Veeam attempts to perform the backup, I get a "strange" error regarding the UUID being unrecoverable:
19/10/2024 14:12:47 :: hassio : Failed to convert [Not Settable] to UUID.

I apologize if this topic has already been discussed, but I tried searching and couldn't find anything. Additionally, I'm still quite new to both Proxmox and Veeam.

Thank you very much!

Davide

Case opened: #07470783

[ManOwaRitis]

Same exact problem here. Community Edition of Veeam, Proxmox v8.2.7 and a Windows Server 2022 Standard VM.

- Thanks.

[PTide]

Hi @DavideC,

It's not clear what does Hyper-V have to do with that. Would you please elaborate on how your infra is built?

Thanks!

[DavideC]

Good morning @PTide,
by “hyper-v” I don’t mean the Microsoft Hyper-V, but rather an abbreviation for “hypervisor.”

My infrastructure is quite simple:
I have a Proliant server running Proxmox, and I am running some virtual machines on it. Among them, I have a Windows Server 2022 machine with Veeam to back up some virtual machines, but it fails.

Davide

[rovshan.pashayev]

Hello Davide,

What do you see in the field of SMBIOS (for the VM which you are trying to backup)?

[DavideC]

Goodmorning rovshan,
i see the uuid of the machine: d2b8****-****-****-****-******1b2bc3
Instead of asterisks there are uuid characters

[rovshan.pashayev]

Hello Davide,

Your initial case was closed automatically as it involved a product using a free license, and the free category is handled on a best-effort basis only.
Please open a new case and upload the logs at https://www.veeam.com/kb1832.

[DavideC]

Hello Rovshan,
i opened a new case with the log as suggested.
New case id: 07496572

[rovshan.pashayev]

Hello Davide,

Great, thank you for letting us know. Please stay in touch with the support team as we have asked them to look into your case closely.

Thanks!

[NCothr]

Good day,

Did you find a solution to this problem? I am encountering the exact same thing.

[rovshan.pashayev]

Hello,

Support team is looking into the issue and they will keep you posted as soon as they have any updates or a solution.

[NCothr]

Have there been any discoveries on this? I tried rebooting the entire Proxmox server and same error.

[rovshan.pashayev]

Hello,

The PVE server must have a system UUID. If you receive a "Not Settable" output for your PVE host, you need to check the BIOS/UEFI settings or firmware.

[DavideC]

Good morning everyone!
Great news: as advised by support over the weekend, I turned off the server and went into the BIOS to look for the UUID field.
In my case, I discovered that the "product id" and "serial" fields of the machine were not configured (they were empty).
I configured them based on my server, and now Proxmox recognizes the UUID, and more importantly, Veeam is now able to perform backups!

Note: In my case, it was necessary to reconfigure the server and the job in Veeam once the BIOS settings were fixed because previously it was failing with this error: *"Object reference not set to an instance of an object.

Thanks to everyone and the support team! I hope this discussion will be helpful to others as well!

Davide

[rovshan.pashayev]

Hello Davide,

Thank you for detailed information.

[NCothr]

This solution worked for me as well. Apparently this is an issue with HP servers, so be aware.

Also word of advice: Remove the Proxmox server and worker VMs from Veeam BEFORE you do this, as for me at least Veeam considered it a new server after getting the UUID and we had a tough time removing the old worker VM and creating a new one after the fact.

[tpayton]

The error "Failed to convert [Not Settable] to UUID." is now documented in https://www.veeam.com/kb4694.