Skip to main content
Question

VBR Proxmox VM-Backup not possible - Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

  • September 14, 2024
  • 2 comments
  • 358 views

Hi all,

 

my first entry here :-)

I use the Community Edition of VBR for backing up two proxmox-vms. Installation was no problem and worker was configured. If I backup linux-vms there is no problem. But if I try to backup two windows server 2022 vms (image for hpe proliant server) i get the error: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). If i check the guid in windows with power shell the guid seems to be good. I tried serveral things but it is not possible to do a backup.

Anybody a solution or the same problem?

 

Daniel

2 comments

jcolonfzenpr
  • Experienced User
  • September 14, 2024

Hi all,

 

my first entry here :-)

I use the Community Edition of VBR for backing up two proxmox-vms. Installation was no problem and worker was configured. If I backup linux-vms there is no problem. But if I try to backup two windows server 2022 vms (image for hpe proliant server) i get the error: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). If i check the guid in windows with power shell the guid seems to be good. I tried serveral things but it is not possible to do a backup.

Anybody a solution or the same problem?

 

Daniel

There are many users complaining about that problem in the proxmox forum.

https://forum.proxmox.com/threads/uuid-lost-after-changing-machine-type.136942/post-633181


  • Author
  • New Here
  • October 8, 2024

Hi Jonathan,

many thanks for the link. But unfortunately no success. In the posts there was said, that they got no UUID checking via powershell. I got the UUID. Also the workaround by inserting the args in the config-files of the VM don’t work. I cloned one VM and testet it but the error still exists. Going back to qemu 8.0 was also not the solution :-(

 

Daniel