How to Use Refurbished Servers for Load Balancing

Load Balancing

Load balancing spreads requests across two or more servers so that no single machine is overloaded and one failure does not take the service down. It is one of the best uses for refurbished servers: instead of one expensive new server, you can run several capable refurbished ones behind a load balancer and gain both capacity and redundancy.

Quick answer: put two or more identical refurbished servers behind a load balancer, such as HAProxy, NGINX or a hardware or cloud balancer, enable health checks so failed servers are taken out of rotation, and keep shared data in a database or storage that all nodes can reach.

How load balancing works

Clients connect to a single address owned by the load balancer. The balancer forwards each request to one of the backend servers according to an algorithm, and constantly checks that each server is healthy. If one stops responding, traffic goes to the others.

AlgorithmHow it chooses a serverBest for
Round robinEach server in turnIdentical servers and similar requests
Weighted round robinIn turn, but stronger servers get moreMixed hardware, such as older and newer refurbished models
Least connectionsThe server with the fewest active connectionsLong-lived connections and uneven request times
IP hash or sticky sessionsThe same client goes to the same serverApplications that keep session state on the server
server load balancing

Why refurbished servers suit load balancing

  • Redundancy for less: two refurbished servers often cost less than one new server of similar power, and you remove a single point of failure.
  • Scale out: add another node when demand grows. See our guide to server scalability.
  • Mixed generations: weighted algorithms let you use older and newer hardware together.
Pro tip: buy matching servers where you can, with the same model, CPU and RAM. Identical nodes are easier to manage, patch and swap, and make simple round robin balancing work well.

Setting up load balancing

  1. Choose the balancer. Software options such as HAProxy and NGINX run on a small server or virtual machine. For critical services, run two balancers with a shared virtual IP (for example with keepalived) so the balancer is not a single point of failure.
  2. Prepare identical backends. Same OS, application version and configuration on every node.
  3. Move shared state out. Store sessions, uploads and data in a shared database, cache or storage that every node can reach.
  4. Configure health checks. Check an application URL, not just whether the server responds to ping.
  5. Test failure. Switch one node off during testing and confirm traffic moves to the others without errors.
  6. Monitor. Watch response times and node health. Our monitoring tools guide compares free options.
Watch out: a load balancer does not protect your data. If all nodes write to one database on one server, that database is still a single point of failure. Plan database replication or backups as part of your high availability design.

Common problems

ProblemLikely causeFix
Users get logged out randomlySessions stored on individual serversUse sticky sessions or move sessions to a shared store
One server overloadedWrong algorithm or weightsSwitch to least connections or adjust weights
Failed server still receives trafficHealth check too basicCheck an application URL and lower the check interval
Different results on different serversConfiguration drift between nodesAutomate deployment so every node is identical
Good to know: load balancing and high availability overlap but are not the same. Load balancing shares work across servers; high availability is the wider design that keeps the whole service running when any part fails.

Frequently asked questions

What is server load balancing?

It is distributing incoming requests across several servers so that no single server is overloaded and the service keeps running if one server fails.

How many servers do I need for load balancing?

At least two backend servers. For critical services, also run two load balancers so the balancer itself is not a single point of failure.

Can I mix old and new servers behind a load balancer?

Yes. Use weighted round robin or least connections so stronger servers take more of the load.

Is HAProxy free?

Yes. HAProxy is open source and widely used for software load balancing. NGINX also offers load balancing in its open-source version.

Building a load-balanced cluster? Configure matching refurbished servers or ask us for volume pricing.

Server Site