VM backup files vanished after the rename

[Mathev]

I am striving to locate the VMs backup files PVE ver8.1.3; kernel 6.5.11.7-pve) because after a VM bulk rename, I experienced the well-known PROXMOX bug:
renamed VMs don't start and all backups disappeared.

I did the restart of the entire machine and checked the obvious backup locations :
/var/lib/vz/images - EMPTY
/var/backups - no files with the VM names

Does anybody know where PROXMOX stores the VM backups??

 

[fiona]

Hi,

I am striving to locate the VMs backup files PVE ver8.1.3; kernel 6.5.11.7-pve) because after a VM bulk rename

what exactly did you do? There is no out-of-the-box feature to change guest IDs in Proxmox VE.

I experienced the well-known PROXMOX bug:
renamed VMs don't start and all backups disappeared.

what bug is that? If you change the ID of a VM of course backups with that ID won't be associated to the VM anymore.

I did the restart of the entire machine and checked the obvious backup locations :
/var/lib/vz/images - EMPTY
/var/backups - no files with the VM names

Does anybody know where PROXMOX stores the VM backups??

It depends on the storage configuration. If you used the local storage, the backups will be in /var/lib/vz/dump. You can also navigate to the storage in the web UI and select the Backup Content tab. If you can't find it, please share the output of cat /etc/pve/storage.cfg.

 

[Mathev]

Hi Fiona,
many thanks for your prompt response.
1)
Mathev: I am striving to locate the VMs backup files PVE ver8.1.3; kernel 6.5.11.7-pve) because after a VM bulk rename
Fiona: what exactly did you do? There is no out-of-the-box feature to change guest IDs in Proxmox VE.
Mathev: I selected the node name and in the node, submenu Options(first row) entered new name (HASSIO >>> OGRODOWA).
the VM didn't start after this step. However after changing it back to HASSIO it behaved same way.


2)
Fiona: what bug is that? If you change the ID of a VM of course backups with that ID won't be associated to the VM anymore.
Mathev: I expected to see the backups of the VM in the Backup submenu with some markings renamed or something similar.
but is vanished :-(.

3) Fiona: (...)please share the output of cat /etc/pve/storage.cfg.



Best regards
M.

 

[fiona]

Hi Fiona,
many thanks for your prompt response.
1)
Mathev: I am striving to locate the VMs backup files PVE ver8.1.3; kernel 6.5.11.7-pve) because after a VM bulk rename
Fiona: what exactly did you do? There is no out-of-the-box feature to change guest IDs in Proxmox VE.
Mathev: I selected the node name and in the node, submenu Options(first row) entered new name (HASSIO >>> OGRODOWA).
the VM didn't start after this step. However after changing it back to HASSIO it behaved same way.

Oh, so you only changed the name not the ID. All the name could affect is the hostname but only in combination with cloudinit. I don't think the renaming was the cause of it not booting anymore.

What is the exact error you get when you try to start the VM. You can double click on the VM <ID> - Start task in the UI and also check the system logs/journal from around the time the issue happened.

Please post the VM configuration qm config <ID> replacing <ID> with the actual ID. What kind of host CPU do you have?

2)
Fiona: what bug is that? If you change the ID of a VM of course backups with that ID won't be associated to the VM anymore.
Mathev: I expected to see the backups of the VM in the Backup submenu with some markings renamed or something similar.
but is vanished :-(.

The backups are grouped by the VM ID, not by name. So changing the name won't affect that. If you select the Backup tab of the VM or the Backup tab of the storage, you should see them.

3) Fiona: (...)please share the output of cat /etc/pve/storage.cfg.
View attachment 61426

You can also check on the CLI in /var/lib/vz/dump. That's where the backups are stored.