Brand new debian 11 machine snapshotting (image backup) error

Hey guys,

I have have installed Debian 11 bullseye (cinammon env) and tried to do a full image backup but something went wrong. When i installed the client i used option (4) for the images, also rebooted the server+client couple of times.
I would very much appreciate it if anyone can help me on this matter.

Server ver: 2.5.27
Client ver: 2.5.22

Command used to install client:

TF=$(mktemp) && wget "" -O $TF && sudo sh $TF; rm -f $TF
sudo urbackupclientctl add-backupdir -d /home/

urbackup.log file:

2022-12-01 16:14:49: ERROR: Not found
2022-12-01 16:14:50: ERROR: Not found
2022-12-01 16:14:51: ERROR: Creating snapshot of "/dev/mapper/root-98d1f8b1f411" failed
2022-12-01 16:14:51: ERROR: Snapshotting device /dev/mapper/root-98d1f8b1f411 via dm...
2022-12-01 16:14:51: ERROR: Layering in dm-era device...
2022-12-01 16:14:51: ERROR: FLOCK_PERM=//.era-meta_3d41c58e-6724-4d47-8981-11c766a08a11
2022-12-01 16:14:51: ERROR: device-mapper: create ioctl on root-98d1f8b1f411-a31725acca86411d-clone-era  failed: Device or resource busy
2022-12-01 16:14:51: ERROR: Command failed.
2022-12-01 16:14:51: ERROR: Creating shadowcopy of "/dev/mapper/root-98d1f8b1f411" failed.
2022-12-01 16:14:51: ERROR: Creating shadow copy failed. See client log file for details.

df -h

Filesystem                     Size  Used Avail Use% Mounted on
tmpfs                          3,2G  3,5M  3,2G   1% /run
/dev/mapper/root-98d1f8b1f411  219G   92G  117G  44% /
tmpfs                           16G  240M   16G   2% /dev/shm
tmpfs                          5,0M  4,0K  5,0M   1% /run/lock
/dev/nvme0n1p2                 466G  331G  135G  72% /media/WindowsDisk
/dev/sda1                      511M   24K  511M   1% /boot/efi
tmpfs                          3,2G  420K  3,2G   1% /run/user/1000
/dev/sdc1                      1,9T  1,5T  388G  80% /media/LinuxUser/Elements
//            476G  366G  111G  77% /home/LinuxUser/Desktop/spa
tmpfs                           16G     0   16G   0% /run/qemu

Thank you in advance

anyone a solution for this?

It seems a bug on linux mint ?