5 Signs Your Business Backup Strategy Is Failing

Most South African businesses that have experienced data loss had backup software. They had scheduled jobs, confirmation emails, and the quiet confidence of knowing their data was protected. What they didn't have was a backup strategy that actually worked when it was needed.

There is a large gap between having backup and having reliable recovery. These five warning signs indicate that your organisation is likely sitting in that gap right now.

1. You've Never Successfully Run a Restore Test

This is the most common — and most dangerous — gap in business backup strategies. A backup job that completes without errors is not evidence that the backup is good. It is only evidence that the job ran. Whether the resulting backup can actually restore your data to a usable state is a completely different question, and the only way to answer it is to test a restore.

Backup corruption, incomplete job runs, database consistency errors, and agent version mismatches are all failure modes that backup jobs routinely complete without flagging. They only become visible when you attempt a restore.

The uncomfortable question: If ransomware encrypted your file server tonight, when was the last time you verified that your backup could restore it fully? If the answer is "I'm not sure" or "never," your backup strategy has an untested assumption at its core — and assumptions are not recovery plans.

A genuine backup strategy includes scheduled restore tests — at minimum quarterly for critical systems — with documented results. Not "the job ran," but "we restored this dataset to a test environment and verified data integrity."

2. Your Backup Is on the Same Network as Your Primary Data

A backup that lives on the same network as the data it is protecting is not a backup — it is a second copy that will be lost in exactly the same incidents as the first.

Ransomware encrypts every accessible storage location it can reach. A NAS device, an external drive connected to a server, a mapped network drive labelled "Backup" — these are not outside the blast radius of an attack on your primary network. They are directly inside it.

Load shedding creates the same problem from a different angle. A power surge or UPS failure during a stage 6 outage can damage primary storage and backup storage simultaneously if they share the same power environment.

The 3-2-1 rule exists for this reason: 3 copies of data, on 2 different media types, with 1 copy off-site or off-network. The off-site copy is what actually saves you. For most South African businesses, that means cloud backup with a provider whose storage infrastructure is not connected to your network.

The question to ask: If someone in your office deleted every file on every on-site storage device right now, would your backup survive?

3. Nobody Is Monitoring Backup Job Failures

Backup jobs fail silently all the time. A licence expires. An agent loses connectivity to the backup server. A volume grows beyond the allocated backup window and the job times out before completing. A changed password breaks the service account running the backup. The job shows "warning" rather than "failed" and nobody reads the warnings.

In organisations without a dedicated IT function — or where IT is a part-time responsibility alongside other duties — backup monitoring is frequently the first thing that falls through the cracks. The backup software sends emails that go to a shared inbox nobody checks. The management console shows amber alerts that have been amber for six months.

The sign this is happening: When last did someone in your organisation look at the backup monitoring dashboard and verify that all protected systems have a current, completed, error-free backup job?

A working backup strategy requires active monitoring, not passive trust. Set up alerts that notify a named individual immediately on failure — not a shared inbox, a named person. Set an SLA: any backup failure must be investigated and resolved within 24 hours.

4. Your Microsoft 365 or Google Workspace Data Isn't Backed Up

A significant number of South African businesses use Microsoft 365 or Google Workspace as their primary business platform — email, documents, calendars, shared drives — and assume that because it is "in the cloud," it is backed up.

It isn't. Microsoft and Google provide resilient infrastructure, not backup. Their shared responsibility models explicitly state that customers are responsible for their own data. Accidental deletion, ransomware that syncs encrypted files to the cloud, admin errors, and departing employee data can all result in permanent data loss that Microsoft and Google cannot recover.

Microsoft 365's recycle bin retains deleted items for up to 93 days. Version history has limits. Neither is a substitute for a point-in-time backup with a multi-year retention window.

If your business runs on Microsoft 365 or Google Workspace and does not have a third-party backup solution covering those platforms, your most business-critical data — the email, documents, and collaborative files your team works in every day — is unprotected.

5. Your Recovery Time Has Never Been Calculated

A backup strategy that cannot tell you how long recovery will take is not a strategy — it is wishful thinking.

Recovery time matters because downtime costs money. For many South African businesses, a single day of complete operational downtime carries costs in lost revenue, staff productivity, customer trust, and SLA penalties that dwarf the annual cost of a proper backup solution. For businesses in financial services, healthcare, or logistics, the costs can be catastrophic within hours.

Your backup strategy should give you two specific numbers:

• Recovery Time Objective (RTO): How long will it take to restore systems to a usable state after a major incident?
• Recovery Point Objective (RPO): How much data can you afford to lose? If backups run nightly, your RPO is up to 24 hours of data.

If you don't know these numbers — or if you know them but have never tested whether your backup infrastructure can actually meet them — your organisation is making a business continuity commitment it may not be able to keep.

---

What a Working Backup Strategy Actually Looks Like

A reliable backup strategy has four properties:

1. Tested — restore tests run on a schedule and results are documented
2. Isolated — at least one copy is off-network and outside the blast radius of an on-site incident
3. Monitored — failures generate immediate alerts to a named owner
4. Scoped — all critical data is covered, including SaaS platforms like Microsoft 365

If your current strategy is missing any of these, you have a gap that will matter at the worst possible time.

Montana Data Company's Build Your Solution configurator lets you specify your environment — server backup, Microsoft 365, endpoints, or a combination — and get an instant cost and coverage breakdown. Most businesses can have a fully tested, off-network backup solution in place within a week.