OOTBI - S3-integrated - Gateway

[MikeD82]

One of my OOTBI appliances does not have line of site to VBR so I need to use a Gateway to connect to it. That makes the type S3-compatible vs S3-integrated. Is S3-integrated supported for gateway connections vs direct

[Andreas Neufert]

Hello Mike,
yes, S3 compatible storage including OOTBI can be added behind the Gateway that you can select at the repository definition. All flow will go through it.
OOTBI has integrated into our Smart Object Storage API that works through the regular S3 operations (and through the gateway).

Does this answer your question?

[MikeD82]

That is the way I have it and it adds as S3-compatible.

[MikeD82]

From Object First help PDF.

5.10 KB0010: SOSAPI Does Not Work
Without Connectivity between Object
First Cluster and VBR
Issue Description
The SOSAPI functionality does not work properly when there is no network connectivity between the Object
First Cluster and the Veeam Backup and Replication.
Even if connectivity is unavailable, it is possible to add a backup repository in gateway mode. Although the
repository can be added successfully, SOSAPI operations will not function due to the lack of a required
communication path.
Product Affected
•
•
Version/Build: Ootbi appliance clusters (all hardware models). Applies to all firmware versions.
Version/Build: Starting from Veeam 12 and later.
Root Cause
SOSAPI requires direct communication between the Object First Cluster and VBR to perform its operations.
Although the system may allow adding a backup repository without confirming full connectivity between
these components, SOSAPI depends on this connection to interact with VBR services. If this connectivity is
absent, SOSAPI cannot complete the required API calls and will not function properly.
Solution
Verify that network connectivity between the Object First Cluster and VBR is correctly configured
and operational.
/help/1.7/kb0002-ports-and-addresses-used-by-object-first/
https://helpcenter.veeam.com/docs/vbr/u ... er=13#osrc
Once connectivity is restored, SOSAPI functionality should resume normal operation.
Workaround
There is no functional workaround that allows SOSAPI to operate without connectivity between the Object
First Cluster and VBR

[MikeD82]

Case #08147334

[Andreas Neufert]

Thanks Mike, let me check on this one with the responsible team members.

[veremin]

Hello Mike,

I checked this with the responsible teams, and your understanding is correct.

Regular S3-compatible object storage connectivity through a gateway server is supported, so the repository can be added and used in gateway mode.

However, SOSAPI/S3-integrated detection currently requires direct connectivity between the Veeam Backup & Replication server and the Object First cluster.

So, in a configuration where VBR does not have direct line of sight to the OOTBI appliance and all communication goes through a gateway server, the repository can be added as S3-compatible, but SOSAPI will not be detected and the repository will not be shown as S3-integrated.

At the moment, the workaround is to ensure direct network connectivity between the VBR server and the Object First cluster if SOSAPI/S3-integrated functionality is required.

We have discussed this internally and created an enhancement request to support SOSAPI through gateway mode in the future.

Thanks for bringing this up!