Skip to main content
Solved

Extract data from backup in S3 Object storage created by Windows endpoint backup


kristofpoppe
Forum|alt.badge.img+9

Hi all,

A user formatted his laptop as revenge to his company, but a valid endpoint backup was taken using Endpoint agent backup for workstation to a dedicated S3 object storage bucket.

So we’re out of meta-data but should have 7 valid backup points in Object Storage.

 

Now I want to get FLR from this backup with minimum effort, so I was thinking of adding the Repo in an Existing VBR 12.1 and import the backups from there.

Attaching the bucket: no problem

Syncing the repo: no problem

Importing backups from the bucket: problem :-(

 

I get the message: Failed to synchronize Object Storage <Object Name> Folder does not exist.

Anybody tried this before ? Another path could be to install the Endpoint agent on a donor machine and try to connect from to the repo and perform restores…

 

Best answer by kristofpoppe

Hi Chris, Thanks for your response.

 

In the meanwhile, I figured out a solution. I’ve added the object storage as Wasabi, since it was Wasabi storage. And this gave the error of the missing folder.

 

I removed the object storage from the VBR inventory and re-added is as generic S3 compatible storage.

This went flawless and I’m able to access the backup.

 

So it seems there are some differences between the Wasabi implementation and the regular S3 compatible implementation imho.

View original
Did this topic help you find an answer to your question?

6 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8464 comments
  • January 9, 2024

It should work to import to VBR for sure but the other method you mentioned about Agent might be worth trying as well.


kristofpoppe
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • 118 comments
  • Answer
  • January 9, 2024

Hi Chris, Thanks for your response.

 

In the meanwhile, I figured out a solution. I’ve added the object storage as Wasabi, since it was Wasabi storage. And this gave the error of the missing folder.

 

I removed the object storage from the VBR inventory and re-added is as generic S3 compatible storage.

This went flawless and I’m able to access the backup.

 

So it seems there are some differences between the Wasabi implementation and the regular S3 compatible implementation imho.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8464 comments
  • January 9, 2024

Glad you found a workaround.


dloseke
Forum|alt.badge.img+8
  • Veeam Vanguard
  • 1447 comments
  • January 12, 2024

This is interesting….I didn’t realize there was much difference between the two other than it pre-filling some information for you.  I’m not sure I would have considered bringing up as regular S3-compatible storage.  I think this would be good to bring up to Support for visibility as well.


Geoff Burke
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • 1317 comments
  • January 12, 2024

@kristofpoppe you might want to add your experience to this thread in the R&D forums as you should be able to add the bucket to a new server without any issues:

 

https://forums.veeam.com/object-storage-as-a-backup-target-f52/veeam-12-sobr-with-vmware-and-wasabi-restore-testing-issues-and-questions-t89194.html


Geoff Burke
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • 1317 comments
  • January 12, 2024

Comment