TechKnowSurge
TechKnowSurge Catalog Videos How Much Redundancy? (N+1)
VideoSecurityFree

How Much Redundancy? (N+1)

High availability depends on having the right level of redundancy, measured using N+1, N+2, or N+N models that define how many spare systems sit alongside active infrastructure. The appropriate redundancy tier balances the cost of additional hardware against the potential revenue impact of unplanned downtime.

⚑ Complete this video to capture a CTF flag worth 1 point.

About this video

High availability is built on redundancy, and the N+1, N+2, and N+N models give IT teams a consistent framework for deciding exactly how much backup capacity to maintain. N+1 means keeping one spare system beyond the number required for normal operations — if two servers are needed to handle production load, a third is held in reserve. N+2 extends that buffer to two additional spares, and N+N represents full duplication, where every active component has an equivalent standby counterpart. These models apply across servers, database instances, network hardware, and any other infrastructure element where failure would affect service continuity. Redundant components don't have to remain offline until failure occurs. In an active-active configuration, the spare capacity participates in normal operations by sharing the workload — two servers each handle half the traffic, and if one goes offline, the other absorbs the full load without interruption. This approach has the added benefit of continuously validating that backup systems are functional, rather than discovering a problem only when a failover is actually needed. Selecting the right redundancy tier is ultimately a cost-versus-risk decision. Higher redundancy levels require proportionally greater hardware investment, and full N+N duplication effectively doubles infrastructure expenses. Organizations weigh that cost against the financial impact of downtime — if an outage translates to significant revenue loss or regulatory exposure, investing in deeper redundancy is straightforward to justify. Environments where brief interruptions are tolerable may find that N+1 provides an adequate safety margin at a fraction of the cost.

What you'll learn

What's covered

Redundancy for High Availability

Key terms

Redundancy
The duplication of critical components or systems to increase reliability and availability.
High Availability
HA
High Availability describes systems designed to operate continuously with minimal downtime, achieved through redundancy, failover clustering, and load balancing to meet the Availability pillar of the CIA triad.
Failover
The automatic switching to a redundant system or component when the primary one fails.
N+1
A redundancy model that specifies one additional backup component beyond the minimum number required to keep a system operational.
N+N
A redundancy model where a full duplicate set of components mirrors every operational component, providing maximum redundancy.
Load Balancer
A device or software that distributes incoming network traffic across multiple servers to ensure availability and performance.

Topics

High Availability Redundancy Models Fault Tolerance Infrastructure Design Disaster Recovery Data Center Operations

Transcript

If we want to achieve high availability, then we're going to need to have some redundancy within our infrastructure. But how much redundancy do we need?

Measuring Redundancy with N+1

Sure, we want redundancy, but the question is how much redundancy do we want? If we need one server, do we set up two servers? Do we set up three servers? Do we set up four servers? How many extra servers do we want to set up?

One of the ways that we measure this is with N+1, or two, or three. What we say is we want to achieve a certain level of having spares available. So N+1 means whatever number we have, we want one more than that.

Let's take a look at a non-technology example of N+1. Let's take a look at a car. What does a car need to go down the road? Well, a car has four tires. And so if we have four tires and it's required to have four tires to go down the road, then we have one spare. N+1 means that we have four - that's the N part of that equation - and the plus one is that extra spare tire to replace one of those tires if it goes flat.

So in this example right here, maybe we need two servers that are up and running. Well, if we need two servers up and running, we're going to have a spare server. So if any one of those goes down, we can move the load and the processing of that server to that third server. Same thing here: we maybe need one database server. And if we just need one database server, then we have one on standby. So this is how many we need, which is one, plus one extra.

So you always have one extra with N+1. N+2 means we have two extra spares. You can see that N+3 is three extra spares, and N+N means that we have a duplicate of everything. So if we have five servers, then we have an extra five servers on standby.

Putting the Spare to Work

Now, in my example of the car, the plus one is something that's not really operational until you put it on. As an example of that, I have four tires on a car, one of them goes bad, I take this spare that was not being used out of the trunk and then I put it onto the car. So that is the plus one right there.

But we could be utilizing that extra spare, that redundancy there. And what does that look like? Well, here we have the need for a server. Let's say we determined we need the use of just one server, but we're practicing N+1, so we add a second server. It doesn't have to be turned off. It could actually be functioning, it could actually be working. And what we do is we just split whatever load we have: half goes to one server and the other half goes to the other server.

What's great about this is that we know that both servers are functioning. And when one goes offline, we just move the 50% of the load that was going to the second server and we move it onto the first server. So this is still an example of N+1.

Choosing How Much

So which one are we actually going to choose? Well, a big part of this is going to come down to cost. Something that has just a little redundancy to it is going to cost much less than something that is fully duplicate. You have to pay for twice as much stuff with this N+N. So a lot of it is just going to be the cost and how much you are willing to spend on it.

The other side of this equation is how much impact is it going to have if you don't have this redundancy? If you have downtime, how much does it impact the business? So if you're going to have a huge amount of revenue loss because you're going to have downtime in IT, then you're going to pay for a lot more redundancy on your network.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →