Redundancy doesn’t mean duplication
When people hear “redundancy,” they often think it means having two of the same thing.
Two generators.
Two devices.
Two identical backups.
That feels logical—but it’s usually the wrong approach.
Identical backups fail together
When two systems rely on the same underlying dependency, they tend to fail at the same time.
If both backups:
Use the same fuel
Depend on the same infrastructure
Require the same access point
They don’t meaningfully reduce risk. They just double down on it.
Redundancy only works when failures are independent, not mirrored.
Better redundancy looks different, not bigger
True redundancy comes from variety, not volume.
Different solutions fail in different ways. That’s the advantage.
One system may be fast but fragile.
Another slower but more reliable.
Together, they cover more scenarios with less effort.
This is why diversity beats duplication.
Keep redundancy simple
If redundancy adds complexity, it’s probably counterproductive.
The best backup plans:
Are easy to remember
Are easy to maintain
Require minimal decision-making under stress
If you have to think hard to use it, it won’t get used.
A simple check
Look at one backup you currently rely on and ask:
Does it fail the same way as the primary?
Does it depend on the same resource?
Would both be compromised by the same disruption?
If yes, it’s duplication—not redundancy.
Replacing one copy with a different approach often reduces risk more than adding another layer.
Preparedness works best when backups are different, not just additional.
— Survivd
