webmasterbeta
New Member
We are in an urgency to setup two to three servers with load balancing ( not costly solutions).
Any company who can manage this at affordable cost welcomSetting up round-robin DNS is extremely easy for load balancing, but not for fail-over purposes. Because even if one of the servers goes down and you remove the IP from the nameserver, it will take a while to work (depending on the TTL).Then what is the best method for fail over servicesyou can use something like Pound or heartbeat.You should be looking at LVS, granted it will only work properly if the servers are at the same datacenter.Setting up round-robin DNS is extremely easy for load balancing, but not for fail-over purposes. Because even if one of the servers goes down and you remove the IP from the nameserver, it will take a while to work (depending on the TTL).
Actually, if multiple IPs are presented and one IP address is offline, most web browsers, etc. should still be able to connect (although perhaps a bit slower initially).We are in an urgency to setup two to three servers with load balancing ( not costly solutions).
Any company who can manage this at affordable cost welcom
Take a look at Softlayer. They offer true hardware load balancing / failover.
Don't use DNS to do load balancing / failover -- doesn't work.Take a look at Softlayer. They offer true hardware load balancing / failover.
Don't use DNS to do load balancing / failover -- doesn't work.
Softlayers load balancing has a connection limit per server.Softlayers load balancing has a connection limit per server.
HA!, that kinda makes it kinda pointless and useless.If all the servers are in a single location, then hardware load balancing is the way to go.
If this is all new for you, then a used alteon is probably more than adequate.
If you interested in distributing the server locations, global load balancing using a geolocation aware dns server would be a good option.I can't change my DC from now, i am with superbhosting.net as of now and i want to do this for my servers
Any company who can manage this at affordable cost welcomSetting up round-robin DNS is extremely easy for load balancing, but not for fail-over purposes. Because even if one of the servers goes down and you remove the IP from the nameserver, it will take a while to work (depending on the TTL).Then what is the best method for fail over servicesyou can use something like Pound or heartbeat.You should be looking at LVS, granted it will only work properly if the servers are at the same datacenter.Setting up round-robin DNS is extremely easy for load balancing, but not for fail-over purposes. Because even if one of the servers goes down and you remove the IP from the nameserver, it will take a while to work (depending on the TTL).
Actually, if multiple IPs are presented and one IP address is offline, most web browsers, etc. should still be able to connect (although perhaps a bit slower initially).We are in an urgency to setup two to three servers with load balancing ( not costly solutions).
Any company who can manage this at affordable cost welcom
Take a look at Softlayer. They offer true hardware load balancing / failover.
Don't use DNS to do load balancing / failover -- doesn't work.Take a look at Softlayer. They offer true hardware load balancing / failover.
Don't use DNS to do load balancing / failover -- doesn't work.
Softlayers load balancing has a connection limit per server.Softlayers load balancing has a connection limit per server.
HA!, that kinda makes it kinda pointless and useless.If all the servers are in a single location, then hardware load balancing is the way to go.
If this is all new for you, then a used alteon is probably more than adequate.
If you interested in distributing the server locations, global load balancing using a geolocation aware dns server would be a good option.I can't change my DC from now, i am with superbhosting.net as of now and i want to do this for my servers