Using cloud storage repository, is VBO used as a network traffic hop during backup?

[cerberus]

Using VBO to backup O365 mailboxes primarily to local storage/repository. VBO is stacked on a dedicated backup server with VBR11.

Looking at options to offload VBO backup data to 3rd party S3 cloud storage (Wasabi).

For anyone doing this, does VBO have to pull the data down to a local repository first before it offloads to cloud repository?

When running a backup job how does the network traffic flow? Is mailbox backup data transferred directly between Microsoft O365 cloud and the S3 storage provider, or is the local server where VBO is installed used as one of the traffic hops (pulls data down from O365 then uploads to S3 storage)?

[Mildur]

The vbo proxy component is the one, which writes vbo backup data to the object storage. Direct Path is not possible.

Data will be downloaded to the proxy and then written to the object storage. It is not stored on the local repo, if you are asking that.

[cerberus]

Thanks, direct path not being possible answers that.

I was hoping to use VBO to do the backup in a direct path sense so that we don't take a hit on the traffic during backups.

[Mildur]

Direct path would need a component installed on the office365 servers, which can send vbo365 data in the veeam format to wasabi. I don‘t think, Microsoft will allow that to happen.