There is a bug in PVE that leads to users that get attached to PVE via an AD domain, once being deletet in AD, remain in the groups they belonged to inside PVE:
https://forum.proxmox.com/threads/user- ... ug.148479/
https://bugzilla.proxmox.com/show_bug.cgi?id=5610
This results in warnings being pushed through the API in front of the JSON container during the management communication with VBR.
As a consequence, backup is not working. The group has to be removed forcefully inside PVE.
Here an example of the communication, VBR carries out against PVE and the extra lines being added, when the situation above occurs:
The two "user config" warnings destroy the communication as VBR seems to expect pure and only JSON.
As this is a know situation, I would be great if VBR could ignore those extra lines and carry on.
Thanks,
Mike
https://forum.proxmox.com/threads/user- ... ug.148479/
https://bugzilla.proxmox.com/show_bug.cgi?id=5610
This results in warnings being pushed through the API in front of the JSON container during the management communication with VBR.
As a consequence, backup is not working. The group has to be removed forcefully inside PVE.
Here an example of the communication, VBR carries out against PVE and the extra lines being added, when the situation above occurs:
Code:
root@mysystem:/home/veeambkp# pvesh get storage/local --output jsonuser config - ignore invalid group member 'myuser@ad_user'user config - ignore invalid group member 'myuser@ad_user'{"content":"iso,images,vztmpl,backup,snippets","digest":"a07db5e6bfb289b44dd60ec431ef2710a8dafee1","path":"/var/lib/vz","shared":0,"storage":"local","type":"dir"}As this is a know situation, I would be great if VBR could ignore those extra lines and carry on.
Thanks,
Mike
Statistics: Posted by mdiver — Oct 23, 2025 12:56 pm
