This is s strange one for me and I hope someone can advise. Environment is updated to PVE9.1 & PBS 4.1
I have a CT with a 12GB root disk + 3x bind mounts on a Proxmox Host, on the same host I have another CT with 32GB root drive and 5x bind mounts (plus a couple of VM's)
The 32GB CT backs up to PBS as expected, but the 12GB CT is going through the process of backing up 2.2TB of data, and although the backup process completes without error, it is extending the backup window by 2 hours additional, and delaying the backups of the VM's which are in the queue after the CT's have completed.
I have verified that the 'bind mounts' are not set to be backed up and they would amount to +30TB if they were included.
I have QTY2 PBS (both encrypted) and get the same results if either of them are the backup target. However if I perform a manual backup to an SMB share, I see that the bind mounts are excluded and the resulting vzdump is only 2.8GB which completes as normal.
This is the log of the final stage of the erroneous backup process:
Notice how the duplicates are 99%.

I am at a loss here, I can't imaging anything within the CT which could cause this fault, but the PBS's and all the other CT's & VM's in my system are functioning as expected.
Any advise would be appreciated.
I have a CT with a 12GB root disk + 3x bind mounts on a Proxmox Host, on the same host I have another CT with 32GB root drive and 5x bind mounts (plus a couple of VM's)
The 32GB CT backs up to PBS as expected, but the 12GB CT is going through the process of backing up 2.2TB of data, and although the backup process completes without error, it is extending the backup window by 2 hours additional, and delaying the backups of the VM's which are in the queue after the CT's have completed.
I have verified that the 'bind mounts' are not set to be backed up and they would amount to +30TB if they were included.
I have QTY2 PBS (both encrypted) and get the same results if either of them are the backup target. However if I perform a manual backup to an SMB share, I see that the bind mounts are excluded and the resulting vzdump is only 2.8GB which completes as normal.
This is the log of the final stage of the erroneous backup process:
Code:
2026-01-03T04:52:34+00:00: successfully added chunk e247b28b3572aba9a4d22b20ceb01be46f331db577118a70a980106fe1597b76 to dynamic index 2 (offset 2206232325532, size 3951214)
2026-01-03T04:52:34+00:00: successfully added chunk 6237ca93869499c4e716a5081f5d8979bc28febf54b2157f53cffb58f88b43bf to dynamic index 2 (offset 2206236276746, size 3290800)
2026-01-03T04:52:34+00:00: upload_chunk done: 10143865 bytes, 6c66e53ba9d7f8b97d3a99ef8f5ecb5c6735468ee1afec407f70f1c6b20556a9
2026-01-03T04:52:34+00:00: PUT /dynamic_index
2026-01-03T04:52:34+00:00: dynamic_append 1 chunks
2026-01-03T04:52:34+00:00: successfully added chunk 6c66e53ba9d7f8b97d3a99ef8f5ecb5c6735468ee1afec407f70f1c6b20556a9 to dynamic index 2 (offset 2206239567546, size 10143865)
2026-01-03T04:52:34+00:00: POST /dynamic_close
2026-01-03T04:52:34+00:00: Upload statistics for 'root.pxar.didx'
2026-01-03T04:52:34+00:00: UUID: 1bde95a787ed4e5c95c9fd93a7f6b237
2026-01-03T04:52:34+00:00: Checksum: 77d9644dcbfa97193f12258f3d3bddc8780c2127a1b0282f5f4718dd1c3edcd9
2026-01-03T04:52:34+00:00: Size: 2206249711411
2026-01-03T04:52:34+00:00: Chunk count: 133206
2026-01-03T04:52:34+00:00: Upload size: 2282131010 (0%)
2026-01-03T04:52:34+00:00: Duplicates: 132188+4 (99%)
2026-01-03T04:52:34+00:00: Compression: 47%
2026-01-03T04:52:34+00:00: successfully closed dynamic index 2
2026-01-03T04:52:34+00:00: POST /dynamic_chunk
2026-01-03T04:52:34+00:00: upload_chunk done: 556866 bytes, 790517ec04db9520e34246823ad14e1945647d5e0d466235a760922010a787f5
2026-01-03T04:52:34+00:00: PUT /dynamic_index
2026-01-03T04:52:34+00:00: dynamic_append 1 chunks
2026-01-03T04:52:34+00:00: successfully added chunk 790517ec04db9520e34246823ad14e1945647d5e0d466235a760922010a787f5 to dynamic index 1 (offset 0, size 556866)
2026-01-03T04:52:34+00:00: POST /dynamic_close
2026-01-03T04:52:34+00:00: Upload statistics for 'catalog.pcat1.didx'
2026-01-03T04:52:34+00:00: UUID: 11a4f357ed5141e2a3640b448dfd764f
2026-01-03T04:52:34+00:00: Checksum: d70cd71da448cef711beca587ec43945d3dd39eb09313f934fd969ab10300dfd
2026-01-03T04:52:34+00:00: Size: 556866
2026-01-03T04:52:34+00:00: Chunk count: 1
2026-01-03T04:52:34+00:00: Upload size: 556866 (100%)
2026-01-03T04:52:34+00:00: Compression: 42%
2026-01-03T04:52:34+00:00: successfully closed dynamic index 1
2026-01-03T04:52:34+00:00: POST /blob
2026-01-03T04:52:34+00:00: add blob "/backup/ct/405/2026-01-03T02:54:33Z/index.json.blob" (483 bytes, comp: 483)
2026-01-03T04:52:34+00:00: POST /finish
2026-01-03T04:52:34+00:00: syncing filesystem
2026-01-03T04:52:46+00:00: successfully finished backup
2026-01-03T04:52:46+00:00: backup finished successfully
2026-01-03T04:52:46+00:00: TASK OK
Notice how the duplicates are 99%.

I am at a loss here, I can't imaging anything within the CT which could cause this fault, but the PBS's and all the other CT's & VM's in my system are functioning as expected.
Any advise would be appreciated.
Last edited: