PBS Client "Partial" access denied but still success?

USER372214

New Member
Dec 4, 2024
2
0
1
Running into an issue running the proxmox-backup-client backup command on a debian 12 bookworm client. The initial backup succeeds, but on subsequent backups the client is showing repetitive failed to open file: "partial": access denied errors, even though the backup still appears to succeed.

Here is a snapshot of the output:

Bash:
user@laptop:~$ proxmox-backup-client backup laptop-home.pxar:/home/user --ns Client
Starting backup: [Client]:host/laptop/2024-12-05T03:22:12Z   
Client name: laptop   
Starting backup protocol: Wed Dec  4 19:22:12 2024   
Downloading previous manifest (Tue Dec  3 21:13:49 2024)   
Upload directory '/home/user' to 'user@pbs!laptop@10.x.x.20:8007:backupPool' as laptop-home.pxar.didx   
failed to open file: "partial": access denied   
... (About 5 more of the above error)   
failed to open file: "partial": access denied   
processed 10.706 GiB in 1m, uploaded 17.635 MiB   
failed to open file: "partial": access denied   
... (repeated)   
failed to open file: "partial": access denied   
processed 18.08 GiB in 2m, uploaded 17.635 MiB   
failed to open file: "partial": access denied   
... (repeated, this chunking happens many more times)
processed 138.388 GiB in 13m, uploaded 55.719 MiB   
laptop-home.pxar: had to backup 70.399 MiB of 153.053 GiB (compressed 29.176 MiB) in 821.86 s (average 87.714 KiB/s)   
laptop-home.pxar: backup was done incrementally, reused 152.984 GiB (100.0%)   
Uploaded backup catalog (62.716 MiB)   
catalog.pcat1: backup was done incrementally, reused 21.74 MiB (34.7%)   
Duration: 822.09s   
End Time: Wed Dec  4 19:45:37 2024

Permissions wise, the User has admin permissions for the datastore, and the token has Datastore.PowerUser for the namespace.

Any Ideas on what "partial" is? Or methodology to discover more information? Looking at the PBS syslog Server side, I see no errors with the backup, and it states that the backup finished successfully.
 
Hi,
Running into an issue running the proxmox-backup-client backup command on a debian 12 bookworm client. The initial backup succeeds, but on subsequent backups the client is showing repetitive failed to open file: "partial": access denied errors, even though the backup still appears to succeed.
these are warnings, showing you do not have access to read some file along the filesystem tree of the directory you are trying to backu up. These will be ignored and not included into the backup snapshot, but are not considered a hard error.

Any Ideas on what "partial" is? Or methodology to discover more information?
I would guess this is a file/directory your local user called user (which runs the backup job), does not have the permissions to access. You can try to run find /home/user -name partial -exec stat {} \; to find out more about these files.

Looking at the PBS syslog Server side, I see no errors with the backup, and it states that the backup finished successfully.
That is expected, as there is no error, the files you do not have access to by the user executing the backup client are skipped as mentioned above.
 
  • Like
Reactions: USER372214
Hey Chris, thank you for your response - You were spot on. The "partial" permission denied error was an old set of containerization files I had messed with, buried deep down in the home directory.

This is pretty awesome, and Thank you and your team for all your hard work. Looking forward for the backup client to support more hosts.

Have a great day and Happy holidays!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!