Urgent Help Needed: Backup Error - "Parameter 'backup-ns' is Unexpected"

[geffin]

Hello Proxmox Community,

I'm encountering a critical issue while attempting VM backups from Proxmox host to Proxmox Backup Server. The error message reads: "VM qmp command 'backup' failed - Parameter 'backup-ns' is unexpected." This error has been consistently preventing successful backups.

I urgently need your guidance to resolve this. Any help, suggestions, or insights are greatly appreciated.

If additional information is required, please let me know.

Thank you all for your assistance!

 

[EllyMae]

Sounds like a bug in PVE. Use your support channels. If you've paid for it, go now to the paid support.

Otherwise, use Bugzilla: https://bugzilla.proxmox.com/

 

[dcsapak]

hi, what's the output of 'pveversion -v' ? how long is the vm already running?

 

[geffin]

Below is the output of pveversion -v:

proxmox-ve: 7.2-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-10
pve-kernel-helper: 7.2-10
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-2-pve: 5.15.39-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1


All the VMs on this host is getting this error. Below is an output when I run the backup manually on one of the VMs on this host:

INFO: starting new backup job: vzdump 100 --storage PBSCT1 --remove 0 --notes-template '{{guestname}}' --mode snapshot --node pmx03
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2023-10-18 16:34:41
INFO: status = running
INFO: VM Name: r2dmail.r2dfuel.com
INFO: include disk 'virtio0' 'HDDPOOL:100/vm-100-disk-0.qcow2' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: skip unused drive 'PVE:100/vm-100-cloudinit.qcow2' (not included into backup)
INFO: skip unused drive 'PVE:100/vm-100-disk-0.qcow2' (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/100/2023-10-18T14:34:41Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (pmx03@pbs != pmx06@pbs)
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 100 failed - VM 100 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (pmx03@pbs != pmx06@pbs)
INFO: Failed at 2023-10-18 16:34:42
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[dcsapak]

first, that version is very old, i'd at least upgrade to the latest 7.4 (for security updates, but also to rule out old bugs)

second, the error is not the same you posted above:

ERROR: VM 100 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (pmx03@pbs != pmx06@pbs)

says that the backup owner of the backup does not match pmx03 vs pmx06

 

[geffin]

Apologies.. did the back up on the wrong VM. I did a manual backup on one of the multiple VMs on the host experiencing this issue:


INFO: starting new backup job: vzdump 120 --storage PBSCT1 --node pmx03 --mode snapshot --notes-template '{{guestname}}' --remove 0
INFO: Starting Backup of VM 120 (qemu)
INFO: Backup started at 2023-10-18 16:42:57
INFO: status = running
INFO: VM Name: capetown.wonderproxy.com
INFO: include disk 'virtio0' 'HDDPOOL:120/vm-120-disk-1.qcow2' 60G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/120/2023-10-18T14:42:57Z'
INFO: skipping guest-agent 'fs-freeze', agent configured but not running?
ERROR: VM 120 qmp command 'backup' failed - Parameter 'backup-ns' is unexpected
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 120 failed - VM 120 qmp command 'backup' failed - Parameter 'backup-ns' is unexpected
INFO: Failed at 2023-10-18 16:43:00
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[Neobin]

A quick search leads to this:
https://forum.proxmox.com/threads/error-backup-of-vm-failed-parameter-backup-ns-is-unexpected.109908
with the solution being this:
https://forum.proxmox.com/threads/proxmox-backup-server-2-2-available.109724/post-471929

 

[geffin]

Here's a brief update:

I successfully resolved the error 'backup' failed - backup connect failed: command error: backup owner check failed (pmx03@pbs != pmx06@pbs).

However, the majority of backups are still failing with the error message:

Backup Error - "Parameter 'backup-ns' is Unexpected."

It's worth noting that certain VMs on the same host are backing up successfully to PBS.

Do you have any other ideas about what might be causing this error, apart from the version of Proxmox running on this host?

 

[VictorSTS]

Backup Error - "Parameter 'backup-ns' is Unexpected."

It's worth noting that certain VMs on the same host are backing up successfully to PBS.

This may indicate that you did update Proxmox to be comatible with namespaces (given your pveversion -v above), but some of your VMs are still using the previous version of the libraries. Try to fully stop one of the VMs that you can't backup and start it again so it uses the currently installed version. Then try to back it up to your PBS storage.