[ovirt-users] long time running backup (hanged in image finalizing state )

Hello there. we have issue with backups on our cluster, one backup started 2 days ago and is is still in state finalizing. select * from vm_backups;              backup_id               | from_checkpoint_id |           to_checkpoint_id           |                vm_id                 | phase |        _create_date        | host_id | des cription |        _update_date        | backup_type |             snapshot_id              | is_stopped --------------------------------------+--------------------+--------------------------------------+--------------------------------------+-------+----------------------------+---------+---- ---------+----------------------------+-------------+--------------------------------------+------------ b9c458e6-64e2-41c2-93b8-96761e71f82b |                    | 7a558f2a-57b6-432f-b5dd-85f5fb9dac8e | c3b2199f-35cc-41dc-8787-835e945217d2 | Ready | 2022-09-17 00:44:56.877+02 |         |         | 2022-09-17 00:45:19.057+02 | hybrid      | 0c6ebd56-dcfe-46a8-91cc-327cc94e9773 | f (1 row) and if I check imagetransfer table, I see bytes_sent = bytes_total. engine=# select it.disk_id,bd.disk_alias,it.last_updated, it.bytes_sent, it.bytes_total  from image_transfers as it , base_disks as bd where  it.disk_id =  bd.disk_id;               disk_id                |                      disk_alias                       |        last_updated        |  bytes_sent  | bytes_total --------------------------------------+-------------------------------------------------------+----------------------------+--------------+-------------- 950279ef-485c-400e-ba66-a3f545618de5 | log1.util.prod.hq.sldev.cz_log1.util.prod.hq.sldev.cz | 2022-09-17 01:43:09.229+02 | 214748364800 | 214748364800 there is no error in logs if i use /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all  -qc  there is no record in any part. I can clean these record from DB to fix it but it will happen again in few days. vdsm.x86_64 4.50.2.2-1.el8 ovirt-engine.noarch 4.5.2.4-1.el8 is there anything i can check to find reason of this ? Thank you Jirka