To all -
I have 3 SOBRs. Each SOBR uses an onsite NAS for the performance tier and S3 for the capacity tier.
With our current S3 provide I have 3 gateways servers, with one server per SOBR / cap tier.
We will be using a new vendor for our S3 storage in Amazon, and they wanted to us the default connection mode of DIRECT to connect to the cap tier. I have 5 proxies that I am considering using in DIRECT mode to fulfill the request or I can use the 3 gateway servers.
My question is, for performance, is there a preference to configure the connection mode to Amazon S3 for gateway vs direct? I want to have the offload processing spread over multiple hosts so either via the proxies or the gateway servers. I am aware, I will need more holes in my FW depending on how many servers I use.
TIA for any answers.
Lewis
-
- Enthusiast
- Posts: 56
- Liked: 5 times
- Joined: Apr 09, 2023 7:50 pm
- Contact:
-
- Veeam Software
- Posts: 889
- Liked: 160 times
- Joined: Feb 16, 2012 7:35 am
- Full Name: Rasmus Haslund
- Location: Denmark
- Contact:
Re: Cap Tier - Connection Mode - Gateway VS Direct
The main challenge with your current setup is that if that one server for a specific SOBR fails, then no data will be sent to your capacity tier. If you added multiple gateway servers or set it to direct, then Veeam can find an alternative server for offloading. Just keep in mind, as you are using a NAS for your performance tier (assuming it is on SMB or NFS), then you are using a mount server regardless, so it would probably make a lot of sense to use the same server as both a mount server and gateway server to avoid east-west traffic.
Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
-
- Product Manager
- Posts: 20679
- Liked: 2383 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Cap Tier - Connection Mode - Gateway VS Direct
Since we are talking about capacity extents, source proxy servers will not play any role in transferring data to them.
If the capacity extent is configured in direct connection mode, the source data mover, which runs either on the source repository itself or on its gateway server (in the case of object storage or file share), will be responsible for sending data to it.
Since, in your case, the source data mover will be running on the gateway server specified in the NAS repository settings, to spread the load across multiple servers, you need to specify multiple gateway servers in those settings (by clicking "Choose" next to the Gateway server field and selecting multiple servers under the "Use the following gateway servers" radio button).
Thanks!
If the capacity extent is configured in direct connection mode, the source data mover, which runs either on the source repository itself or on its gateway server (in the case of object storage or file share), will be responsible for sending data to it.
Since, in your case, the source data mover will be running on the gateway server specified in the NAS repository settings, to spread the load across multiple servers, you need to specify multiple gateway servers in those settings (by clicking "Choose" next to the Gateway server field and selecting multiple servers under the "Use the following gateway servers" radio button).
Thanks!
Who is online
Users browsing this forum: Semrush [Bot] and 9 guests