The biggest mistake we see isn’t a lack of backup.
It’s a lack of redundancy.
More specifically, people look at the cost of putting redundancy in place, but not the cost of not having it.
That’s where things start to go wrong.
Start With a Simple Question
If a key system went down tomorrow, how long could your business operate without it?
A few minutes?
A few hours?
A full day?
In a lot of manufacturing environments, the honest answer is:
“We can’t.”
What This Looks Like in Practice
Your biggest order is due to go out.
The system handling it stops working.
Production slows or stops completely.
Staff are still on site.
Orders begin to back up.
Customers are waiting.
Even if the system comes back later, the damage doesn’t disappear.
You’re still dealing with delays, missed commitments and the effort needed to catch up.
The Cost of Downtime
We regularly see single failures causing serious disruption.
Not because data is lost, but because the business can’t operate while systems are being rebuilt.
For example, we’ve seen situations where a server fails, the data is available, but rebuilding the environment takes far longer than expected.
The system eventually comes back.
But by that point, production has been interrupted, staff have been waiting, and the knock-on effects are already in motion.
Why Backups Aren’t the Same as Redundancy
Most businesses we speak to do have backups.
That’s a good thing.
But backups don’t keep you running.
They help you recover after the fact.
That’s a very different outcome.
Where the Delay Comes From
If a server fails and all you have is a backup, the process looks like this:
- The fault has to be identified
- Hardware needs repairing or replacing
- The system has to be rebuilt
- Data is restored
That can take hours or days depending on the issue.
During that time, the business is often waiting.
One Question Most People Avoid
Are your backups actually tested?
Because a backup that hasn’t been tested isn’t really a backup.
It’s an assumption that it will work when you need it.
What Proper Redundancy Looks Like
Redundancy is about keeping things running, not just recovering them.
A typical setup might include:
- Local backups
- Replication to the cloud
- A secondary system capable of taking over
That secondary system might be:
- A standby server
- A replicated virtual environment
- A cloud-based failover environment
The exact setup depends on the business, but the outcome is the same.
If the primary system fails, you switch over and continue operating.
When Things Go Wrong Without Hardware Failure
It doesn’t always take a server failure to cause disruption.
We’ve seen situations where:
- An update affects one system
- That impacts another
- Which then causes further issues elsewhere
What started as a routine change becomes a wider problem.
In one case, multiple systems had to be run from backup infrastructure just to keep things going.
That wasn’t a disaster scenario.
That was a normal working day that went wrong.
Understanding Recovery Time
When businesses start looking at this properly, two practical questions come up:
- How quickly do systems need to be back?
- How much data can you afford to lose?
In simple terms:
- Some businesses need systems back in minutes
- Others can manage for a few hours
The problem is, many don’t make that decision until after something has failed.
Redundancy Isn’t Just About Servers
his applies across your whole setup.
Internet
If your connection goes down:
- Do you have a backup line?
- Does it fail over automatically?
Waiting for a provider fix can still mean a full day offline.
Network
If a switch fails, it can take out:
- Wi‑Fi
- Devices
- Entire areas of the network
Do you have something ready to replace it?
Or are you trying to fix it while everything is down?
(We covered this in more detail here: Why Network Switches Matter | Affirm IT Blog)
The Difference That Matters
There’s a big difference between:
“Swap it over and carry on”
and
“Let’s work out what’s broken”
That difference is usually measured in hours or days.
A More Practical Way to Think About It
Redundancy doesn’t mean duplicating everything.
It means answering one question clearly:
If something fails, how do we keep operating?
Final Thoughts
The cheapest solution is usually only cheap until something goes wrong.
That’s when you find out what it actually costs.
Backups protect your data.
Redundancy protects your ability to operate.
They are not the same thing.
FAQ
Are backups enough on their own?
No. Backups help recover data, but they don’t keep systems running during a failure.
What is redundancy in IT?
It means having systems in place that allow your business to continue operating if something fails.
How quickly should systems recover?
That depends on your business, but if recovery takes days, it’s usually a risk.
What’s the difference between backup and failover?
Backup restores data after a failure. Failover keeps things running by switching systems.
Do all businesses need redundancy?
Not to the same level, but every business needs a plan for what happens when something fails.
Need Help?
At Affirm IT, we start with practical questions:
- What happens if your main system fails?
- How long would recovery actually take?
- Which systems are critical?
- Where are your single points of failure?
From there, we put the right level of resilience in place so your business continues operating when things go wrong.
If you’re not confident in your worst-case scenario, get in touch with us. At Affirm IT, we specialise in providing comprehensive IT support for small businesses in Heanor, Ripley, Ilkeston, Eastwood and all over the UK
