Backup Basics: What "Business Continuity" Actually Covers
Poseidon Network Systems · Cape Town
"We do backups" is one of the most common and least useful things an IT provider can tell a business owner, because a backup on its own doesn't answer the question that actually matters: if something goes wrong tomorrow, how long is the business down, and what, if anything, is lost for good?
Backup vs. disaster recovery vs. business continuity
A backup is a copy of your data, stored somewhere separate from the original. On its own, a backup tells you nothing about how quickly you'd get that data back into a working system.
Disaster recovery is the plan for restoring systems after something fails, hardware failure, ransomware, fire, theft, a burst pipe in the server room. It answers: how do we get back online, and from what point in time?
Business continuity is the broader picture: what keeps the business operating while recovery is happening. Can staff work remotely from a backup location? Is there a fallback phone line? Can invoices still go out? A backup is one ingredient in business continuity, not the whole plan.
The two numbers that actually matter
Any serious continuity conversation comes down to two figures:
RPO (Recovery Point Objective), how much data you could lose. If backups run nightly and something fails at 4pm, you've lost a day's work. Backups every few hours shrink that gap.
RTO (Recovery Time Objective), how long you can afford to be down. An hour is a very different plan, and cost, to a weekend.
Most small businesses have never had either number stated out loud, let alone tested. That's the actual gap, more often than the backups themselves being absent.
Questions worth asking your IT provider
Where do backups live, onsite only, offsite only, or both? Onsite-only backups don't survive theft or fire at the same premises.
How often do backups actually run, and when was the last one verified by actually restoring from it (not just checking a completed-successfully log)?
If the office became inaccessible tomorrow, could staff keep working, and from where?
Is there a written recovery time estimate, or is "how long would it take" an unanswered question?
If any of these draw a shrug, that's the sign continuity hasn't been designed, only backup has, and only partly.
How we handle it
Our approach pairs offsite, verified backups with remote-first support, because for most SMEs, the fastest continuity plan is being able to get a technician working on the problem immediately over remote access (AnyDesk) rather than waiting for someone to physically arrive. For most day-to-day incidents, that turns a same-day site visit into a same-hour fix.
Not sure what your current setup actually covers? Request a quote for a straightforward backup and continuity review, we'll tell you plainly what's covered, what isn't, and what it would take to close the gap.