So you’re running Proxmox and you have storage for the node on an NFS share somewhere. When you get a container or VM from somewhere else and upload it, lazy style like me, it might end up with the wrong ownership if you do it like this:
- Make an NFS share just for Proxmox on the NAS, and don’t bother to also map it on your PC so you can upload to it directly.
- Take the lazy way out and put the VM or container somewhere you do have mapped (like a generic media folder) and then use the TrueNAS shell to move it over to where Proxmox can see it.
- The shell will set ownership to whoever you’ve logged in as, and probably not the owner you want.
The result is the Proxmox backup utility will be trying to chown files in a container which itself doesn’t have the right ownership to allow it. Rsync will blow up with error 22 and your backup will die.
The fix? Go into the NAS, go to that file, and chown it to the right user. It’s probably whichever owner:group has the other files which do back up correctly, not whatever user you DECIDED randomly to use for the move operation.
For a folder with the image in it:
chown -R user:group folder name
This will change ownership of the folder (200, in this case) and the actual image.
Now test backups, it’ll probably work.
And you probably won’t map that share to make it easier next time, because why would you. Nobody ever gives you containers to run, and you shouldn’t even if they did because you can’t know what’s in them.