High availability (HA) is designing a service so that it keeps running when a component fails. Instead of relying on one server, HA spreads the work and the risk across several, so a failed drive, power supply, server or even a whole rack does not take the service down. Refurbished servers make this kind of redundancy far more affordable.
Common high availability architectures
| Architecture | How it works | Good for |
|---|---|---|
| Active-passive failover | A standby server takes over when the primary fails | Databases, file servers, applications that cannot run on two nodes at once |
| Active-active with load balancing | Several servers share live traffic | Web applications and stateless services |
| Hypervisor cluster | VMs restart on another host if one fails | Small businesses running several workloads |
| Database replication | Primary and replica databases kept in sync | Critical databases |
| Multi-site | Services run or can fail over to a second location | Protection against site-wide outages |

Remove single points of failure, layer by layer
| Layer | Redundancy to add |
|---|---|
| Server components | RAID, dual hot-swap power supplies, redundant fans, ECC memory |
| Servers | Two or more nodes per critical service |
| Storage | Shared storage with redundant controllers, or replicated storage |
| Network | Two switches, teamed server ports, redundant uplinks |
| Power | Two power feeds or circuits, UPS, generator or inverter |
| Internet | Two providers or a backup link |
Building HA with refurbished servers
- Choose identical refurbished servers so any node can replace another.
- Use a hypervisor cluster (for example Proxmox VE, Hyper-V failover clustering or VMware) or application-level clustering.
- Provide shared or replicated storage that every node can reach.
- Add load balancing for web services. See load balancing with refurbished servers.
- Monitor every node and set alerts. Our monitoring guide compares tools.
High availability reduces downtime from everyday failures; disaster recovery covers the big events. Plan both, using our disaster recovery planning guide and our explanation of uptime SLAs.
Frequently asked questions
What is a high availability server?
A server set up as part of a redundant design, usually a cluster, so that the service continues if the server or one of its components fails.
How many servers do I need for high availability?
At least two for the service itself. Some cluster technologies need three nodes, or two nodes plus a witness, to avoid split-brain situations.
What is the difference between high availability and disaster recovery?
High availability keeps services running through component failures; disaster recovery restores services after major events such as fire or ransomware.
Can refurbished servers be used for high availability?
Yes. Identical refurbished enterprise servers make cost-effective cluster nodes, as they include redundant power, RAID and remote management.
Building a cluster? Configure matching refurbished servers or ask us for volume pricing.


