Loadbalancer.org is both a virtual and hardware-based appliance that distributes network traffic through out multiple servers in order to increase the dependability and proficiency of existing users. Therefore, by enabling the Loadbalancer.org application, we are able to deploy our solution in a cluster to ensure overall reliability of the Netsweeper solution. The key benefits that the Loadbalancer.org application will have for Netsweeper includes higher availability, easier maintenance, and enhanced performance overall.
- High-Availability – If a single Netsweeper becomes unavailable, the service will not be interrupted
- Maintenance – Easy to manage as Netsweeper can easily be removed and added to/from the cluster if needed for maintenance purposes
- Performance – For enhanced performance, additional Netsweeper’s can easily added to the cluster
- The recommended load balance deployment type for Netsweeper is a Layer 4 Direct Routing (DR) mode, which is a highly dynamic resolution best suited for Netsweeper web filters and Netsweeper proxies services. There are alternative methods of deployment as well and deciding what deployment mode best fits your requirements comes with a variety of considerations. With a Layer 4 load balancer, it can oversee the information within the network of the Netsweeper Web filter and/or Netsweeper Proxy service. The load balancer inspects the application protocol stack and the balances this with the service’s IP address.
- The three modes supported by Loadbalancer.org include:
- Explicit Mode – proxy settings are explicitly set on each client device. Browser settings on client PCs or other web browser must be changed to point at the Virtual Service IP (VIP) of the load balancer.
- Transparent Mode – policy-based routing is used on the router/firewall that handles client traffic. These rules at the router/firewall make sure that the required traffic (typically HTTP & HTTPS on port 80 & 443) is sent transparently to the load balancer.
- Non-Transparent Mode – proxy settings are explicitly set on each client device. Browser settings on client PCs must be changed to point at the Virtual Service (VIP) on the load balancer.