The following are logged error messages when the VTL assumed an out of space condition
messages:Dec 25 16:20:37 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO130L7 size 262144
messages:Dec 26 10:56:42 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO142L7 size 262144
messages-20221204:Nov 28 00:20:04 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO146L7 size 262144
messages-20221204:Nov 28 10:50:32 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO132L7 size 262144
messages-20221204:Nov 28 10:51:50 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO147L7 size 262144
messages-20221218:Dec 11 16:22:14 vtl kernel: WARN: bdev_alloc_for_pgdata:5862 Cannot find a free bint for tape LTO127L7 size 262144
What most likely has happened is that due to the failed writes Veeam is probably finding an inconsistent metadata. You could try cataloging these tapes individually and then erase them if there is no meaningful data on them. Or you could simply write protect these tapes so that they are not used in the backups.
The problem you earlier faced isn't seen in the logs yet, but might come back later.