VeeamZip backup moved to new repository through SOBR no longer in configuration database

[stuartmacgreen]

I think I have hit the limitation of VeeamZip within B&R. Let me explain.

I took a VeeamZip of a VM. I want to keep it for a few months. The VM is deleted from main source.
I chose a repository, also used by backup jobs.

Weeks later...
I had to perform a change of format for this repository volume.
So used the Migrate backup data through a SOBR repository technique.
Create a SOBR with the new volume repository and add the old volume repository.
Place old repository into Maintenance and do the Evacuate action.
Once complete I remove the new repository.
Map my backup jobs to the new repository.
Remove the SOBR, highlights that it still has backup records against this SOBR - one of the records is the VeeamZip entry.
I proceed.

I did a rescan of the new repository expecting the VeeamZip backup record to re-appear... alas no.

This standalone backup is now outside of Veeam and no way for me to import it, as of course it is not a Backup Job, and doesn't have a .vbm file.
So have lost trackability of the backup file now.

What should I have done to keep traceability of this while at the same time being able to move this around my repository infrastructure?
Export backup?


Thanks

[Gostev]

Stuart, please investigate this with support. Regardless of everything you did, I don't see how it is possible that the rescan process does not pick up a VeeamZIP backup file that is physically present in the repository. Thanks!

[stuartmacgreen]

Rescanned the repository one more time. Still did not appear.

I have then used the (forgotten!) Import Backup option and selected the file that way.
All is good. It is showing under the Disk (VeeamZIP) tree view.