Backup fails with Resource deadlock avoided.

If you check the backup job log for errors hopefully it will tell you more details.  Logs are here - C:\ProgramData\Veeam\Backup

Also recommend contacting support as well.

Hi @tonylee - what kind of backup are you doing? Linux VM with VBR? Linux Agent?

Is this maybe some kind of appliance-based VM? I think I helped someone else a few mos back who had a ‘special’ kind of VM they weren’t able to backup. I don’t recall them having the same error you have shown here, but what I did see was a snapshot wasn’t able to be taken for Veeam to be able to backup the VM...if indeed this is a VM. Nothing really Veeam can do here as it’s a 3rd party appliance. What I suggested the other person to do, if they could, was to power down the VM so a snapshot could be taken by Veeam to do the backup. I’m not sure you can do this with your VM. 

Or, again...is this a physical server you’re trying to backup with a Linux Agent?

Hi, This is a physical server.

Hi @tonylee - I thought of a couple other things you can check. The VAL requires software to be on the Linux system you’re attempting to backup. Look at the VAL System Requirements for the additional software which should be installed on the system you’re trying to backup. Also note, official supported Linux systems says Centos 7 only is supported. I’m not sure a 7.x version is officially supported. Lastly, long-time Community Hub member and blog post guru Michael Paul shared some great info about Linux Agent which might be useful. You can read about it in the link below.

Try those few things then see if you can get your system to backup, and let us know.

RE : HI~ I haven't solved it yet.
The dkms status below is not found. Do I need to install dkms?

[root@biz ~]# (hostnamectl||uname -a)

Static hostname: biz.dentium.com

Icon name: computer-server

Chassis: server

Machine ID: 95e14c6c83984ec58862c1388deb455b

Boot ID: 9aa46b2acee7499cb1db187b01270196

Operating System: CentOS Linux 7 (Core)

CPE OS Name: cpe:/o:centos:centos:7

Kernel: Linux 3.10.0-1160.el7.x86_64

Architecture: x86-64

[root@biz ~]# cat /etc/*release

CentOS Linux release 7.9.2009 (Core)

NAME="CentOS Linux"

VERSION="7 (Core)"

ID="centos"

ID_LIKE="rhel fedora"

VERSION_ID="7"

PRETTY_NAME="CentOS Linux 7 (Core)"

ANSI_COLOR="0;31"

CPE_NAME="cpe:/o:centos:centos:7"

HOME_URL="https://www.centos.org/"

BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"

CENTOS_MANTISBT_PROJECT_VERSION="7"

REDHAT_SUPPORT_PRODUCT="centos"

REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.9.2009 (Core)

CentOS Linux release 7.9.2009 (Core)

[root@biz ~]# (rpm -qa||dpkg-query -l) | egrep –i '(veeam|dkms|kernel-headers|kernel.*devel|linux-image|linux-headers)' | sort

kernel-devel-3.10.0-1160.el7.x86_64

kernel-headers-3.10.0-1160.el7.x86_64

kmod-veeamsnap-6.0.3.1221-1.el7.x86_64

veeam-6.0.3.1221-1.el7.x86_64

[root@biz ~]# dkms status

-bash: dkms: command not found

[root@biz ~]# mokutil --sb-state

SecureBoot disabled

[root@biz ~]# mokutil --list-new

MokNew is empty

[root@biz ~]# find /lib/modules -name '*veeam*' -exec ls -ld {} +

-rw-r--r-- 1 root root 332703 Jun 30 23:31 /lib/modules/3.10.0-1062.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 332703 Jun 30 23:32 /lib/modules/3.10.0-1127.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 332703 Jun 30 23:32 /lib/modules/3.10.0-1160.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 327263 Jun 30 23:31 /lib/modules/3.10.0-123.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 327343 Jun 30 23:31 /lib/modules/3.10.0-229.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 327359 Jun 30 23:31 /lib/modules/3.10.0-327.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 327359 Jun 30 23:32 /lib/modules/3.10.0-514.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 328295 Jun 30 23:32 /lib/modules/3.10.0-693.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 329807 Jun 30 23:32 /lib/modules/3.10.0-862.el7.x86_64/extra/veeamsnap.ko

-rw-r--r-- 1 root root 332303 Jun 30 23:32 /lib/modules/3.10.0-957.el7.x86_64/extra/veeamsnap.ko

[root@biz ~]# lsmod | grep -i veeam

veeamsnap 179888 0

[root@biz ~]# modinfo veeamsnap

filename: /lib/modules/3.10.0-1160.el7.x86_64/extra/veeamsnap.ko

supported: external

version: 6.0.3.1221

description: Veeam Snapshot Kernel Module

author: Veeam Software Group GmbH

license: GPL

retpoline: Y

rhelversion: 7.9

srcversion: 914D02A731AB17A3DC93FE6

depends:

vermagic: 3.10.0-1160.el7.x86_64 SMP mod_unload modversions

signer: Veeam Software Group GmbH

sig_key: C2:87:4E:82:F1:FB:27:75:33:C6:40:8A:B5:36:2F:EE:26:AB:8E:30

sig_hashalgo: sha256

parm: zerosnapdata:Zeroing snapshot data algorithm determine. (int)

parm: debuglogging:Logging level switch. (int)

parm: logdir:Directory for module logs. (charp)

parm: logmaxsize:Maximum log file size. (ulong)

parm: cbtdata:Parameters for persistent CBT. (charp)

parm: snapstore_block_size_pow:Snapstore block size binary pow. 20 for 1MiB block size (int)

parm: change_tracking_block_size_pow:Change-tracking block size binary pow. 18 for 256 KiB block size (int)

parm: fixflags:Flags for known issues (uint)

[root@biz ~]# modprobe -vvv veeamsnap

modprobe: INFO: custom logging function 0x40a3e0 registered

modprobe: INFO: context 0xd8c290 released

Hi @tonylee - yes. Please review the System Requirements. I posted the link in my previous comment above. DKMS, and a host of other modules, are required.