Veeam backup failed since new packages installed on debian pve - error qmp socket - timeout

[mathloggs]

Since this packages installed or upgraded, veeam backup failed
name: bat vim lsb-release psmisc screen sudo needrestart snmpd nmap net-tools unattended-upgrades bind9-dnsutils

error messages on veeam: Failed to perform backup: Failed to connect the NBD server to the hypervisor host

error messages on pve: VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries


update pve to this kernel doesnt solve the issue:
pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.8.12-13-pve)
pve-manager: 8.4.12 (running version: 8.4.12/c2ea8261d32a5020)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8.12-14-pve-signed: 6.8.12-14

 

[Sviat]

Hello,

It looks like its known issue for this backup software related to lock.
To resolve this issue and allow the job to complete for powered-off VMs, reconfigure the Veeam Plugin for Proxmox to lock VMs during backup, informing the CRM not to trigger a stop operation.

1. On the Veeam Backup Server, open the AppSettings File:
   C:\Program Files\Veeam\Plugins\PVE\Service\appsettings.json
   
   
2. Find the line containing <strong>"LockVmOnBackup": false</strong> and change it to <strong>true</strong>.
3. Save the file.
4. Ensure there are no active Proxmox backup or restore tasks.
5. Disable all scheduled Proxmox jobs.
6. Restart the veam PVE Service service.
7. Enable all disabled jobs from Step 5.

 

[mathloggs]

hello,
Thanks for reply

i set the "LockVmOnBackup": to <strong>true</strong> and this seems to solve the issue for the backpup of one VM but another one is still failed.
The QMP socket is slow to respond, and we’re seeing repeated SSH connection failures during backup operations.
Here are the most relevant veeam error logs in :

[ProxmoxBackupManager]: Failed "ssh connect to Proxmox node 10.xxxxxx with ip 10.xxxxxx:22". Error: "Connection reset by peer"<br>System.Net.Sockets.SocketException (104): Connection reset by peer<br>

This error repeats multiple times despite retry logic being in place. Additionally, snapshot creation fails with:
Failed to create a snapshot file for "VeeamTmp_102_drive-scsiX": The backup snapshot storage path is not specified<br>

The QMP socket does eventually respond, but the delays seem to cause timeouts in Veeam

a lot of error messages like this on the PVE during the backup
Sep 17 12:18:17 pa4-pxmx pvestatd[1491]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Sep 17 12:18:27 pa4-pxmx pvestatd[1491]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries

 

[ssevasta]

I am having the same issue. I opened a case with veeam support and they asked me to speak to proxmox. If i enable the LockVmOnBackup option, vms start to fail. Same errors as above.

 

[Johannes S]

I opened a case with veeam support and they asked me to speak to proxmox.

Did they also mention what they expect the Proxmox developers to do? I mean it's not like the Proxmox devs could have a look into Veeams source Code to figure out where things went south

 

[ssevasta]

Did they also mention what they expect the Proxmox developers to do? I mean it's not like the Proxmox devs could have a look into Veeams source Code to figure out where things went south

unfortunately they did not. All they said is that they are using proxomx API