[SOLVED] Backup owner check failed. But I was checked..

[aydoganatakan]

Hello.

I researched this issue a lot. There are pages and pages of articles in different languages.
However, I still haven't found a solution.
I wanted to open a new topic as a solution.

I'm getting the same error like everyone else. However, there is no backup for this VM or even one with the same VMID in the area where I am trying to take a backup.

I can easily make backups for other VMs. But I can't get backup for PVE with VMID 102.

I would like to share a few screenshots about this.





Currently the authorized server starting with "turhost" only backs up to the location seen as "diskalani2".

The authorized server starting with "cloudvist" only backs up to "diskalani1".

I had previously taken a different VM backup to this folder. However, I deleted them. I think it was like that after that.

Could there be a piece of the old backup I took and deleted left on the disk or in a temporary storage area?
Where should I check? I would be very grateful if anyone can help.

Edit:
Additionally, I am attaching a screenshot of the "diskalani2" field. There is no VM102 there either.

BTW: I also did the "start garbage collection" tasks...

 

[Chris]

Hello.

I researched this issue a lot. There are pages and pages of articles in different languages.
However, I still haven't found a solution.
I wanted to open a new topic as a solution.

I'm getting the same error like everyone else. However, there is no backup for this VM or even one with the same VMID in the area where I am trying to take a backup.

I can easily make backups for other VMs. But I can't get backup for PVE with VMID 102.

I would like to share a few screenshots about this.

View attachment 58535

View attachment 58537

Currently the authorized server starting with "turhost" only backs up to the location seen as "diskalani2".

The authorized server starting with "cloudvist" only backs up to "diskalani1".

I had previously taken a different VM backup to this folder. However, I deleted them. I think it was like that after that.

Could there be a piece of the old backup I took and deleted left on the disk or in a temporary storage area?
Where should I check? I would be very grateful if anyone can help.

Edit:
Additionally, I am attaching a screenshot of the "diskalani2" field. There is no VM102 there either.

BTW: I also did the "start garbage collection" tasks...

View attachment 58539

Hi,
there probably is the leftover owner file containing the previous owner in the datastore. On the command line, navigate to the backing path for the datastore in question and check if there is a file <datastore>/vm/102/owner. If so, remove the file or update the owner contained witin it.

Please also paste your exact package version proxmox-backup-manager version --verbose.

 

[aydoganatakan]

Yes, as you said, the non-related VM registration was still there.
I deleted it as a folder. I tried the backup again and now it's running smoothly.

Thank you very much for the information you provided.

proxmox-backup-manager version --verbose

proxmox-backup                2.3-1        running kernel: 5.15.102-1-pve
proxmox-backup-server         2.4.1-1      running version: 2.4.1
pve-kernel-helper             7.3-8
pve-kernel-5.15               7.3-3
pve-kernel-5.15.102-1-pve     5.15.102-1
ifupdown2                     3.1.0-1+pmx3
libjs-extjs                   7.0.0-1
proxmox-backup-docs           2.4.1-1
proxmox-backup-client         2.4.1-1
proxmox-mail-forward          0.1.1-1
proxmox-mini-journalreader    1.2-1
proxmox-offline-mirror-helper unknown
proxmox-widget-toolkit        3.6.5
pve-xtermjs                   4.16.0-1
smartmontools                 7.2-pve3
zfsutils-linux                2.1.9-pve1

 

[Chris]

proxmox-backup 2.3-1 running kernel: 5.15.102-1-pve

Seems like you are missing a reboot to get the latest available version for that PBS host.

Also, I tested deleting a groups on my PBS instance (that however has the latest version), and there the issue with the leftover owner file is not present.

 

[aydoganatakan]

I rebooted. But the output did not change.

proxmox-backup                2.3-1        running kernel: 5.15.102-1-pve
proxmox-backup-server         2.4.1-1      running version: 2.4.1
pve-kernel-helper             7.3-8
pve-kernel-5.15               7.3-3
pve-kernel-5.15.102-1-pve     5.15.102-1
ifupdown2                     3.1.0-1+pmx3
libjs-extjs                   7.0.0-1
proxmox-backup-docs           2.4.1-1
proxmox-backup-client         2.4.1-1
proxmox-mail-forward          0.1.1-1
proxmox-mini-journalreader    1.2-1
proxmox-offline-mirror-helper unknown
proxmox-widget-toolkit        3.6.5
pve-xtermjs                   4.16.0-1
smartmontools                 7.2-pve3
zfsutils-linux                2.1.9-pve1

There are many warnings in the mission history.

2023-11-15T03:34:30+03:00: starting apt-get update
2023-11-15T03:34:37+03:00: Hit:1 http://ftp.tr.debian.org/debian bullseye InRelease
Hit:2 http://ftp.tr.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org bullseye-security InRelease
Err:4 https://enterprise.proxmox.com/debian/pbs bullseye InRelease
  401  Unauthorized [IP: 51.79.228.122 443]
Reading package lists...

2023-11-15T03:34:37+03:00: WARN: E: Failed to fetch https://enterprise.proxmox.com/debian/pbs/dists/bullseye/InRelease  401  Unauthorized [IP: 51.79.228.122 443]
E: The repository 'https://enterprise.proxmox.com/debian/pbs bullseye InRelease' is not signed.

2023-11-15T03:34:46+03:00: TASK WARNINGS: 1

I will do some research on this issue and solve it.

 

[leo1]

I hit the same issue, then I solved it by:
root@pbs1:/mnt/datastore/backup/ct/114#nano owner
changed leo@pbs to root@pam then it worked well.