---
title: "High availability (HA)"
description: "High availability (HA) designs systems to survive failures. Learn about redundancy, failover, clustering and the availability nines that measure uptime."
url: "https://nodea.io/en/glossary/high-availability"
lang: "en"
updated: "2026-07-13"
---

# High availability (HA)

> High availability (HA) is an approach to designing infrastructure that minimizes downtime through redundancy and automatic failover. The goal is to keep a service running even when an individual component fails.

**High availability** (HA) is a set of design practices aimed at keeping a service running continuously despite the failure of individual infrastructure components. Rather than relying on a single server, disk or network link, an HA architecture duplicates critical parts and automates traffic redirection so users never notice an interruption. Availability is expressed as a percentage — the so-called 'nines' — where 99.9% means a few hours of downtime per year and 99.999% just a few minutes.

## How high availability works

HA rests on three pillars. The first is **redundancy**: eliminating single points of failure (SPOFs) by duplicating servers, power supplies, disk controllers and network paths. The second is **failover** — a mechanism that detects a fault and automatically reroutes traffic to a healthy node, typically using a [load balancer](https://nodea.io/en/glossary/load-balancer) or a floating virtual IP. The third is **state synchronization**: data must stay consistent across nodes, achieved through database [replication](https://nodea.io/en/glossary/replication) and shared or distributed storage.

In practice, servers are joined into a [cluster](https://nodea.io/en/glossary/cluster) whose nodes continuously exchange heartbeat signals. A missing heartbeat is treated as a failure and triggers a switchover. A key concern is avoiding the 'split-brain' condition, where two nodes both believe they are active and corrupt shared data.

## Practical application

High availability is standard wherever downtime causes real losses: online stores, banking systems, SaaS platforms, and DNS or mail servers. Typical deployments include a primary-replica database pair with automatic promotion of the replica, an application cluster behind a load balancer, and geo-redundancy that spreads the service across multiple data centers.

When designing HA, it pays to pair it with defined [RTO and RPO](https://nodea.io/en/glossary/rto-and-rpo) targets and with [uptime monitoring](https://nodea.io/en/glossary/uptime-monitoring) that measures real availability and alerts on incidents. For VPS and dedicated servers, HA is most often delivered as a cluster of nodes with load balancing and cross-location data replication.

### What does 99.99% availability actually mean?

It's known as 'four nines' and allows roughly 52 minutes of downtime per year. Each additional nine dramatically shrinks the tolerable outage: 99.9% permits almost 9 hours annually, while 99.999% allows only about 5 minutes.

### How is high availability different from a backup?

HA keeps a service online in real time, instantly shifting traffic to a healthy node after a failure. A backup is a point-in-time restore copy — it protects against data loss, but restoring from it takes time and does not guarantee continuous operation.

## Related

- [Load balancer](https://nodea.io/en/glossary/load-balancer)
- [Cluster](https://nodea.io/en/glossary/cluster)
- [Replication](https://nodea.io/en/glossary/replication)
- [Uptime monitoring](https://nodea.io/en/glossary/uptime-monitoring)
- [RTO and RPO](https://nodea.io/en/glossary/rto-and-rpo)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/high-availability.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)