We've been using both Veeam and PBS for some time. We use PBS to backup every hour throughout the work day and Veeam for a nightly image after work hours. The two don't conflict and things were running fine until early last week when the Veeam backup just started failing with the following error.:
5/16/2025 1:56:37 PM :: JobBoss : qemu-img: Could not open '/mnt/pve/QNAP_NVME/images/800/VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': Could not open '/mnt/pve/QNAP_NVME/images/800/VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': No such file or directory
1. I have verified that the file does exist.
root@pve1:/mnt/pve/QNAP_NVME/images/800# ls
VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2 vm-800-disk-0.qcow2 vm-800-disk-1.qcow2
2. Of the three images for VM800, only the Veeam file does not return details for the "qemu-img" info command.
Happy qcow2 file:
root@pve1:/mnt/pve/QNAP_NVME/images/800# qemu-img info vm-800-disk-0.qcow2
image: vm-800-disk-0.qcow2
file format: qcow2
virtual size: 128 KiB (131072 bytes)
disk size: 592 KiB
cluster_size: 65536
Snapshot list:
ID TAG VM_SIZE DATE VM_CLOCK ICOUNT
1 TestSnap 0 B 2024-10-28 13:54:55 0025:43:59.400 --
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
<snip>
Unhappy qcow2 file:
root@pve1:/mnt/pve/QNAP_NVME/images/800# qemu-img info VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
qemu-img: Could not open 'VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': Could not open 'VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': No such file or directory
So both Veeam and Proxmox think the file doesn't exist, even though it exists in the directory listing.
root@pve1:/mnt/pve/QNAP_NVME/images/800# ls -la VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
-rwxr-xr-x 0 root root 983564288 May 13 19:03 VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
I opened a ticket with Veeam, but their support has not followed up since I submitted additional details. Just curious if anyone has seen or dealt with an issue like this before.
5/16/2025 1:56:37 PM :: JobBoss : qemu-img: Could not open '/mnt/pve/QNAP_NVME/images/800/VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': Could not open '/mnt/pve/QNAP_NVME/images/800/VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': No such file or directory
1. I have verified that the file does exist.
root@pve1:/mnt/pve/QNAP_NVME/images/800# ls
VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2 vm-800-disk-0.qcow2 vm-800-disk-1.qcow2
2. Of the three images for VM800, only the Veeam file does not return details for the "qemu-img" info command.
Happy qcow2 file:
root@pve1:/mnt/pve/QNAP_NVME/images/800# qemu-img info vm-800-disk-0.qcow2
image: vm-800-disk-0.qcow2
file format: qcow2
virtual size: 128 KiB (131072 bytes)
disk size: 592 KiB
cluster_size: 65536
Snapshot list:
ID TAG VM_SIZE DATE VM_CLOCK ICOUNT
1 TestSnap 0 B 2024-10-28 13:54:55 0025:43:59.400 --
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
<snip>
Unhappy qcow2 file:
root@pve1:/mnt/pve/QNAP_NVME/images/800# qemu-img info VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
qemu-img: Could not open 'VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': Could not open 'VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2': No such file or directory
So both Veeam and Proxmox think the file doesn't exist, even though it exists in the directory listing.
root@pve1:/mnt/pve/QNAP_NVME/images/800# ls -la VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
-rwxr-xr-x 0 root root 983564288 May 13 19:03 VeeamTmp_800_drive-sata0_32a41131-a1f9-413b-86a3-c18fa704c4a6.qcow2
I opened a ticket with Veeam, but their support has not followed up since I submitted additional details. Just curious if anyone has seen or dealt with an issue like this before.