Backup after enable OTP

T

TobiWanKenobi

New Member
Aug 12, 2024
21
0
1
Hello everyone,

I just can't figure out what I'm doing wrong. I have secured access to Proxmox and the Proxmox Backup Server with OTP. Since then, my backups are no longer running. I have connected to the backup server using an API key and can see and access the storage.

When I start a backup, I get the following message:


ERROR: VM 102 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam!backup != root@pam)
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 102 failed - VM 102 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam!backup != root@pam)
INFO: Failed at 2025-02-26 10:03:26
 
Hi Chris, i`m to stupid :-)

1740571703790.png

Unfortunately, I can't follow the description of how to do this in the UI. I don't understand it. Sorry if I'm being stupid, but I'm quite new to Proxmox
 
TobiWanKenobi said:
Hi Chris, i`m to stupid :-)

View attachment 82920

Unfortunately, I can't follow the description of how to do this in the UI. I don't understand it. Sorry if I'm being stupid, but I'm quite new to Proxmox
Click to expand...
You will have to provide the default repository if you did not set it up for the cli by passing it via `--repository user@realm@hostname:datastore`, see https://pbs.proxmox.com/docs/backup-client.html

But way easier in the WebUI: Navigate to your Datastore, select the Contents tab, select the backup group (vm/102) in the tree view and click on the icon looking like a person (in the Actions column), there you can then select the correct owner.
 
OK, now I understand it, but only after I backed up a VM created after the OTP change. Unfortunately, I don't have an entry on the datastore for VM102 where I can change the owner


1740574226786.png
 
NFO: starting new backup job: vzdump --storage proxmoxBU --node proxmoxVE --prune-backups 'keep-last=5' --fleecing 0 --notes-template '{{guestname}}' --all 1 --mode snapshot
INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2025-02-26 13:56:36
INFO: status = running
INFO: VM Name: Mint-intern
INFO: include disk 'scsi0' 'local-zfs:vm-102-disk-0' 64G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/102/2025-02-26T12:56:36Z'
ERROR: VM 102 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam!backup != root@pam)
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 102 failed - VM 102 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam!backup != root@pam)
INFO: Failed at 2025-02-26 13:56:36
INFO: Starting Backup of VM 9000 (qemu)
INFO: Backup started at 2025-02-26 13:56:36
INFO: status = running
INFO: VM Name: Debian-Template
INFO: include disk 'scsi0' 'save:9000/vm-9000-disk-0.qcow2' 64G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/9000/2025-02-26T12:56:36Z'
INFO: started backup task 'b7cfcdc3-4737-4330-aeca-a8661ce478b4'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: created new
INFO: 2% (1.8 GiB of 64.0 GiB) in 3s, read: 630.7 MiB/s, write: 5.3 MiB/s
INFO: 11% (7.2 GiB of 64.0 GiB) in 6s, read: 1.8 GiB/s, write: 4.0 MiB/s
INFO: 25% (16.4 GiB of 64.0 GiB) in 9s, read: 3.0 GiB/s, write: 1.3 MiB/s
INFO: 37% (23.8 GiB of 64.0 GiB) in 12s, read: 2.5 GiB/s, write: 2.7 MiB/s
INFO: 49% (31.8 GiB of 64.0 GiB) in 15s, read: 2.7 GiB/s, write: 1.3 MiB/s
INFO: 63% (40.8 GiB of 64.0 GiB) in 18s, read: 3.0 GiB/s, write: 0 B/s
INFO: 77% (49.7 GiB of 64.0 GiB) in 21s, read: 3.0 GiB/s, write: 8.0 MiB/s
INFO: 91% (58.8 GiB of 64.0 GiB) in 24s, read: 3.0 GiB/s, write: 5.3 MiB/s
INFO: 100% (64.0 GiB of 64.0 GiB) in 26s, read: 2.6 GiB/s, write: 0 B/s
INFO: backup is sparse: 60.37 GiB (94%) total zero data
INFO: backup was done incrementally, reused 63.92 GiB (99%)
INFO: transferred 64.00 GiB in 26 seconds (2.5 GiB/s)
INFO: adding notes to backup
INFO: prune older backups with retention: keep-last=5
INFO: running 'proxmox-backup-client prune' for 'vm/9000'
INFO: pruned 0 backup(s)
INFO: Finished Backup of VM 9000 (00:00:27)
INFO: Backup finished at 2025-02-26 13:57:03
INFO: Backup job finished with errors
TASK ERROR: job errors
 
TobiWanKenobi said:
OK, now I understand it, but only after I backed up a VM created after the OTP change. Unfortunately, I don't have an entry on the datastore for VM102 where I can change the owner


View attachment 82928
Click to expand...
As what user are you logged into the WebUI? Does that user have the permissions to see the full datastore contents?
 
Do you maybe have an empty group vm/102 in your datastore? Check the contents of that group via cli by running ls -laR <path-to-datastore>/vm using the full path your datastore is located at. If there is an empty group, you can delete the vm/102 folder or edit the owner file contained within it manually.

If this is the case, than this might be a leftover from manual intervention, empty groups are removed by default.
 
Last edited:
  • Like
Reactions: Johannes S
You must log in or register to reply here.
Top Bottom