+10Hi all,
A customer’s device is complete gone, but has daily full backups stored via CloudConnect in Wasabi. When we try to import the backups, it gives the message ‘No backups found’. Altough, the Cloud Connect server gives usage of the bucket and de job just ran fine. Any ideas how to import the backup in the Cloud Connect server to start the recovery ?
The import of the backup doesn’t seem to find the backup chain….
Best answer by kristofpoppe
I’ve added the repo to a fresh VBR server (no Cloud Connect server) and performed and inventory and import of the backups. Then the restore points showed up in Object storage (imported backups)
From this place, I was able to perform a restore to an hypervisor, open the backup to cherry-pick some files.
Important note: When u use the same keyset for the bucket as the original keyset on the Veeam CC server, the original job will fail and will tell you the bucket is managed by another server. You could fix this by using a new keyset on the same bucket.
+21Do you not require the metadata that sits on block storage to know how to read the data in Wasabi? The data is in chunks so VCC probably does not know how to map them to import the backups. Checking to see if there is any other information I can find.
+21Found this page in the help with some caveats for importing backups to VCC - Importing Backups Manually - User Guide for VMware vSphere
+10Hi Chris, I was thinking the same. I did a rescan of the repo first. As soon as you perform the import backups, you can’t perform it a second time. The option is then gone.
+10I’ve added the repo to a fresh VBR server (no Cloud Connect server) and performed and inventory and import of the backups. Then the restore points showed up in Object storage (imported backups)
From this place, I was able to perform a restore to an hypervisor, open the backup to cherry-pick some files.
Important note: When u use the same keyset for the bucket as the original keyset on the Veeam CC server, the original job will fail and will tell you the bucket is managed by another server. You could fix this by using a new keyset on the same bucket.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
