This Blog is for anyone wanting to load balance the Exchange 2010 CAS role using only open source software.
Does it seem like some appliance vendors go out of their way to make hardware recovery and licencing as difficult as possible?
The BEAST attack is a practical attack based on a protocol vulnerability and mainly affects the client side.
Any engineer dealing with PCI DSS compliance issues probably looses a little bit of the joy in life.
Microsoft Print Server provides a great way to share printers throughout your organisation, but when the print server falls over, the phone quickly starts to ring.
This script was designed primarily to be tied into Ldirectord but feel free to adapt it to your needs, and if you do make changes dont be a stranger post your adaptations below!
I get quite frustrated with benchmarks because they are very hard to perform properly, and even when you do them properly its very hard to get any useful data from them.
There’s been a lot of debate here in the office about how best to capture both your Loadbalancer’s IP and the Source IP of the user in your access_log in Apache 2.4. This is the tried and tested method we've come up with.
Although it's not technically a standard, the X-Forwarded-For (XFF) header is incredibly useful if you have any kind of proxy in front of your web servers.
OK, Before the flames start let me state the usual caveat, "GSLBs don't ALWAYS suck. Just most of the time".
A couple of customers asked if our appliances would do G-Zip compression. In the past we hadn't given it much thought until someone offered us a card to test it!
I’m excited and slightly scared by our latest product! Excited because I've become slightly addicted to launching multiple instances in different parts of the world and load balancing the traffic seamlessly. Scared because this could change our whole business model.
The vast majority of layer 4 load balancers use LVS in two-arm NAT mode.
Here at Loadbalancer.org we have recently started the certification process of our product with Microsoft Office Communications Server (OCS).
When you have users depending on Windows Terminal Services for their main desktop, it's a good idea to have more than one Terminal Server. RDP, however, is not an easy protocol to load balance.
I've previously blogged about how to get TPROXY and HAProxy working nicely together, but what if you want to terminate SSL traffic on the load balancer to use HAProxy to insert cookies in the standard HTTP stream to the backend servers?
Some vendors make a fair bit of hype about their products enabling 99.999% availability out of the box.
If you use HAProxy as the load balancer then all of the backend servers see the traffic coming from the IP address of the load balancer.
Standard Kernel builds of LVS (Linux Virtual Server) don't have the ability to load balance traffic that is from the local node.
One of the (many) traditional problems with load balancing is the requirement to change your infrastructure in order to implement a hardware load balancer.
Direct Routing aka. Direct Server Return (DSR) aka. N-Path is a great load balancing method. And it is, without doubt, the fastest method possible.
Hardware marketing execs get very excited about the fact that their product can magically scale your application by using ‘amazing Layer 7 technology’ in the load balancer such as cookie inserts and tracking/re-writing.