The biggest mistake we see in manufacturing businesses isn’t a lack of backup.
It’s a lack of redundancy.
More specifically—people look at the cost of redundancy, but not the cost of not having it.
And that’s where things start to go wrong.
Start With the Real Question
If a key system went down in your business tomorrow…
How long could you operate without it?
A few minutes?
A few hours?
A full day?
Because in a lot of manufacturing environments, the answer is:
“We can’t.”
The Real Cost of Downtime
We regularly see situations where a single failure ends up costing tens of thousands of pounds.
And that’s before you even consider the reputational impact.
Imagine this:
What does that actually cost?
Not just lost production.
But:
That’s the real cost people don’t factor in.
Why Backups Alone Aren’t Enough
Most businesses we speak to do have backups in place.
That’s a good thing.
But the type of backup matters.
Often we see:
All of those are fine—until the server itself fails.
Because at that point, you’re not restoring data.
You’re rebuilding infrastructure.
And that takes time.
If a component fails on a server that’s a few years old:
That could easily take two or three days.
Can your business afford that?
Are your backups even tested?
That’s another uncomfortable question.
Because a backup that hasn’t been tested isn’t really a backup—it’s a theory.
What Proper Redundancy Looks Like
A proper setup doesn’t just store backups.
It allows you to keep running.
That means:
So if your main server fails, you don’t wait days.
You switch over.
And you carry on working.
We even validate this daily by checking that those backups can actually start the servers—so in a worst-case scenario, there are no surprises.
When Things Go Wrong (Even Without Failure)
It doesn’t always take a hardware failure to cause a problem.
We’ve seen situations where a simple update creates a chain reaction.
An update to one server impacts another.
That server then triggers issues elsewhere.
And suddenly, multiple systems are affected.
In one case, we ended up running three servers from the backup infrastructure just to keep the business operational.
That wasn’t a disaster scenario.
That was a normal working day that went wrong.
Would your business survive that?
Redundancy Isn’t Just About Servers
Once you start thinking about it, redundancy applies across your whole environment.
Internet Connectivity
If your business relies on internet access for orders, systems, or VOIP phones:
Even “next business day” support still means a full day of downtime.
Network Infrastructure
Take something simple like a switch.
If that fails, it could take out:
Have you got a spare ready to go?
Or would you be trying to rebuild it under pressure?
(We covered this in more detail here:
Why Network Switches Matter More Than You Think)
Because the difference between:
“Swap it over and carry on”
and
“Let’s try and figure this out”
…is usually hours of downtime.
The Reality Check
Redundancy doesn’t mean duplicating everything.
You don’t need two laptops per person.
You don’t need two of everything.
But you do need a plan.
If something fails:
How do you keep operating?
Final Thoughts
The cheapest solution is often only cheap in the short term.
Because when something goes wrong, that’s when you find out what it really costs.
Downtime is expensive.
Planning isn’t.
Need Help?
At Affirm IT, we take a practical approach to business continuity and redundancy. We don’t start with complexity—we start with simple questions:
From there, we put the right level of redundancy in place—so your business keeps running when things go wrong.
If you’re not confident in your worst-case scenario, don’t hesitate to
get in touch with us.
