PDM running in LXC and doesn't verify when all backups are verified.

lanepark5033

Member
Feb 20, 2025
49
4
8
The process starts with a backup of the lxc's and vm's listed in the single node, followed by a prune of the PVC and after a delay a verify of the node is performed.
when examining the verify the backup of the PDM LXC has not been verifyed. I can force the verify of the "failing" LXC but it should have been verified along with the other LXC's and VM's in said node.
Verify log attached.
 

Attachments

The process starts with a backup of the lxc's and vm's listed in the single node, followed by a prune of the PVC and after a delay a verify of the node is performed.
when examining the verify the backup of the PDM LXC has not been verifyed. I can force the verify of the "failing" LXC but it should have been verified along with the other LXC's and VM's in said node.
Verify log attached.
Forgot to mention the lxc in question is 302.
 
Just to confirm, by PDM do you mean Proxmox Datacenter Manager?

Also, is CT 302 the LXC container running Proxmox Datacenter Manager, and is it on the same PVE host whose backups are being verified?

What backup solution are you using for this workflow? Is this a Proxmox Backup Server datastore with a scheduled verification job?
 
Just to confirm, by PDM do you mean Proxmox Datacenter Manager?

Also, is CT 302 the LXC container running Proxmox Datacenter Manager, and is it on the same PVE host whose backups are being verified?

What backup solution are you using for this workflow? Is this a Proxmox Backup Server datastore with a scheduled verification job?
Yes PDM means Proxmox Datacenter Manager.
Yes, LXC 302 is the container running PDM and is on the same PVE whos backup are being verified.
Yes the backup solution is a scheduled PVE backup to a PBS and are then pruned, followed by a scheduled verify.
The PBS is onsite along with the PVE. The PVE in question is one of 2 PVE's in the enviornment. The PBS is a physically seperate PC running PBS.
 
Attached is backup job log, shows errors and is probably why the verify failed. I've fixed the error in the job log, but will have to wait until Sat AM for the next sequence of backup/prune/verify/garbageCollection to occur and I'll check backup then to update and hopefully close this item.
 

Attachments