Agent>S3 backup to be recovered via VBR - files missing error - still working

[mdiver]

Maybe just a heads up for development.

We just faced the requirement to cross-recover a backup created towards Wasabi directly from an agent (V6). Recovery is done from within VBR into a VMware VI.
The workload was to be recovered as a VM (->Instant-Recovery).

First we tried to use a read-only user created in Wasabi. This doesn't work. A "cannot access" error is shown.
Interestingly this works, when recovering a VBR->S3 from another VBR where the bucket is introduced read-only.

So we went with a full access user in Wasabi. Now it works.
But still a warning is flagged: "backup files missing". Despite that - the recovery works with P2V conversion.
The warning by the way is also shown, when e.g. doing a Guest-File-Recovery.

Thanks,
Mike

[Dima P.]

Hello Mike,

Any chance you have a case ID to share? Thank you!

[mdiver]

Sorry. As it worked finally, customer refrained from filing a case.

Is it supported at all to:
- backup directly from Agent to a dedicated bucket in S3
- re-map the object repo to VBR
- recover with P2V from it

I'd assume there to be a slightly different structure in the S3 repo when the agent directly backs up to it.

[Dima P.]

Understood, I'll share your feedback with our QA team. Thank you!