Backup with Veeam failing (Disk Size=null)

C

caroline

New Member
Dec 22, 2025
1
0
1
Hi everyone,
we're evaluating PVE as replacement for or ESX environment.
Currently, we're struggling with Backups via Veeam failing because of volume size being reported as "null".
So, the Veeam support asked me to run the API call they use for getting the machine information via my local browser.

REST Response from Browser:
{"data":[{"ctime":"1767620148","format":"qcow2","content":"images","vmid":1000,"size":540672,"volid":"BLN:vm-1000-disk-0.qcow2"},{"content":"images","format":"qcow2","ctime":"1767620149","volid":"BLN:vm-1000-disk-1.qcow2","size":53687091200,"vmid":1000},{"content":"images","format":"qcow2","ctime":"1767620150","volid":"BLN:vm-1000-disk-2.qcow2","vmid":1000,"size":4194304}]}

REST response received by Veeam:
2026-02-13 09:51:35.3466 00010 [22308] DEBUG | [ProxmoxNode][pollux][34323550-3939-5a43-4a44-303330303846]: ==> Response "Get" "https://xxx.yyy.zz:8006/api2/json/nodes/xxx/storage/BLN/content?vmid=1000", "code: 200 - OK", duration: "178 msec", headers: "[]", cookies: "[]", body: "{"data":[{"volid":"BLN:vm-1000-disk-0.qcow2","vmid":1000,"size":null,"content":"images","ctime":"1767620148","format":"qcow2"},{"ctime":"1767620149","format":"qcow2","content":"images","vmid":1000,"size":null,"volid":"BLN:vm-1000-disk-1.qcow2"},{"content":"images","format":"qcow2","ctime":"1767620150","volid":"BLN:vm-1000-disk-2.qcow2","vmid":1000,"size":null}]}"

Can anyone assist me on where to start troubleshooting here?

Thank you very much in advance,
Caroline
 
Hi,

A couple of quick things that might be worth checking:

1. Are you using the same account when logging in via the browser and when Veeam connects to the Proxmox API?
If the accounts are different, it could potentially be a permission issue affecting the API response.

2. Which Veeam version are you running?
I previously had some issues when using an older Veeam version for Proxmox restore operations, and upgrading to a newer version resolved the problem.

It might be helpful to confirm these first.
 
gfngfn256 said:
Another interesting differential.
Click to expand...
There are 3 disks in the VM, they have different ctime's. The value is the same across API responses for corresponding disks.

That said, OP should use the latest Veeam "agent"/patch for PVE. And make sure that the PVE version is in the supported list for Veeam level.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: gfngfn256 and Johannes S
It is possible that OP did not permission the user/token properly. A quick way to check is to run:
curl -k \
-H "Authorization: PVEAPIToken=<USER>@<REALM>!<TOKENID>=<SECRET>" \
https://<PVE_HOST>:8006/api2/json/nodes/<NODE>/storage/<STORAGE>/content?vmid=<VMID>

If null is returned, vs proper size when using root - its a permission issue.
Code: 
TICKET=$(curl -sk -d "username=root@pam&password=YOUR_PASSWORD" \
https://pollux:8006/api2/json/access/ticket | jq -r '.data.ticket')

curl -k -b "PVEAuthCookie=$TICKET" \
"https://pollux:8006/api2/json/nodes/pollux/storage/BLN/content?vmid=1000"


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: pulipulichen
You must log in or register to reply here.
Top Bottom
Back