Following are some common cases with suggested deployments; all of these cases use a Route-Path deployment.
- The Barracuda Load Balancer provides Layer 4 load balancing of TCP/IP traffic.
- The Barracuda Load Balancer provides Layer 4 load balancing of UDP traffic.
- The Barracuda Load Balancer provides SSL offloading and Layer 4 load balancing of TCP/IP traffic.
- Use a one or two-armed Route-Path with one or more Secure TCP Proxy Services. If you use one-armed Route-Path, you will not need to reconfigure the IP addresses of the Real Servers. Two-armed Route-Path provides better performance.
- The Real Servers are on the same subnet as the Barracuda Load Balancer and the configuration cannot be changed.
- Use one-armed Route-Path with a TCP Proxy Service (or a Secure TCP Proxy Service if SSL offloading is required). Or, if almost all of the traffic is outbound, use Direct Server Return with a Layer 4 Service.
- There is an existing IT infrastructure using Windows where the web servers need to communicate with systems such as Active Directory Domain Services, ISA Servers or domain controllers. To avoid changing those network settings, either:
- Use one-armed Route-Path with a TCP Proxy Service.
- Use Direct Server Return with a Layer 4 Service.
- The outbound traffic is far greater than the inbound traffic, for example, if the Real Servers are providing streamed audio or visual media.
- Use Direct Server Return with a Layer 4 Service to increase throughput.
- There is a need to remotely administer the Real Servers individually.
- Create new Services, each of which only load balances a single Real Server.
- Deploy the Real Servers in a one-armed mode where they are on the WAN side of the Barracuda Load Balancer and serving a TCP Proxy Service.
- Or, deploy the Real Servers on the WAN side in Direct Server Return mode serving a Layer 4 Service.
- Deployment Options
- Route-Path Deployment Options
- One-Armed Route-Path Using TCP Proxy, UDP Proxy, or a Layer 7 Service Type