Server load balancing

I have installed a zentyal server behind which i have configured two webservers.
now i want to forward traffic on these two webservers from zentyal (connected to internet) with load balancing using apache feature of the zentyal.
anybody here to help me with the same?

 

Zentyal is based on Ubuntu, so I think you can try this tutorial: http://www.howtoforge.com/setting-u...lancer-with-haproxy-heartbeat-on-debian-lenny

 

Well, thanks for your response but it totally confusing thread. Instead, i have installed 'pound' on the zentyal server today and it is working fine so far

 

mod_proxy_balancer module

but it would have been great if anybody had helped me with mod_proxy_balancer module configuration of apache.

 

Take a look here: http://www.howtoforge.com/load_balancing_apache_mod_proxy_balancer

 

little bit confusing

well, that is a good post but a bit confusing!
can i use server local IPs instead of http1.exemple.com and http2.exepmle.com?
i dont want to make the load balancing backend webserver dependent coz in future i need to make hell lot of changes with backend webservers. moreover my backend servers are WINDOWS based not linux based. Also, in future i am making stickyness more robust by implementing the same through backend DB servers. so it would have been great had the post stated which commands i need to omit to make it simple load balancer without stickyness...

Regards

 

default file gets restored upon system reboot

Hello Falko,

Even though the following method of load-balancer works for me, however the file 'default' gets restored to factory-contents upon system reboot

http://www.howtoforge.com/load_balancing_apache_mod_proxy_balancer

Any idea?

Regards

 

Do you mean /etc/apache2/sites-available/default? I think you can give the file a different name, e.g. /etc/apache2/sites-available/www.example.com.vhost.

 

replacing?

you mean i should rename the original file default?
are you sure that we we will be able to load-balance our traffic?

anyways..i will try and let you know!
thanks.

 

No, leave the default file in its original state and create a new file for your vhost (e.g. /etc/apache2/sites-available/www.example.com.vhost).

 

already tried

Thanks for reply,

Well... i tried that already and that doesn't work for me as my backend webservers are WINDOWS based so i doubt that may be creating any issue but when i tried ur formula mentioned here, it worked but the issue of default file getting restored...m totally confused!!!

Any idea what could be a posible feasible solution?

Regards