If you add the blob repo and rescan it the backups should import.

Thanks Chris, So just to ensure we are on the same page, our blob storage data is not vib file etcs. It’s random looking data. Nothing like the local performance tier files. Do you still expect it will understand it?

You will add it as Object Storage repo and then it will rescan it and show up under Object (Imported) in the tree probably.  Since it was Veeam data it should be understood by Veeam as long as you have the same version which wrote to it originally (v11 or v12).

Yes, object storage is comprised of the blocks of data from the backup files, and is not the actual backup files itself.  This makes is much more space efficient because you aren’t keeping duplicate blocks that you would typically have.  

As a case in point, I have a client that had existing Veeam backups on a NTFS backed repository that was consuming 29.8TB.  I placed a copy of this data in Wasabi object storage for an offsite immutable copy and when it was all said and done, it consumed 15.4TB of space.  Clearly this is quite efficient.  

Back to your question, as Christ noted, once you’ve reconnected to the storage bucket, it should rescan the data and be able to reassemble the backup information based off of the metadata and associated blocks of data in the repo and then it will import that backup data into the configuration database.