Mapping an orphaned backup chain to a new job

[Moebius]

Greetings,
I had an iSCSI repository that ran out of space recently. The repository is the target of a backup copy job for about 150 vms and is using per-machine backup files.
I moved one chain of a large vm to a different iSCSI repository. That is, I moved all .vbk and .vib files to the new repo. After that, I removed the vm from the "Disk (copy)" view under Backups.

Now, a rescan of the new repository finds no backups, and no backup appears in the "imported" view (maybe because there is no .vbm file in the folder?). So it is not possible to map a new job to it.

The moved chain is rather long and I wouldn't like to lose it, even if I know that it is possible to import a single vbk file. Any solution?

[Mildur]

Hi Lucio

The vbm file is needed for mapping backup jobs to backup files.

I think, veeam support has some tools to recreate the vbm file with the help of the backup files.