Backup Copies to S3

If “Direct” is selected, the repository holding the source data will connect directly to to the S3 target, as opposed to if you select a “Gateway”, the traffic will be routed via that server instead. This may be necessary if you have some proxy system in place where the repository doesn’t have direct access to the internet, or if you want the traffic to flow over a specific link.

For cases where storage systems are used that require a gateway server to be selected, like a Data Domain for example, “Direct” will route via the gateway server specified in the settings of that repository.

If you’re using Direct, you don’t need to worry about a Gateway server, as Veeam connects directly to Backblaze. However, if you want to use a Gateway server, make sure the proxy settings are correctly configured on both VBR and Backblaze, ensuring the Veeam server has the necessary permissions and access. For better performance and ease of setup, Direct connection is typically recommended unless you have a specific need for a Gateway server. It’s also worth checking if any specific network/firewall configurations are needed for seamless connection with Backblaze.

Hi,

it depend of your design. If proxy servers has direct access to the S3, then you can use direct. But if you have S3 somewhere, where only VBR and and gateways have, then direct connect mode will not fly.

For example: in my design proxy servers do not have 3rd vlan and only vbr with gateway have. So for me direct mode does not fly for my design.