Back to Insights

Business Continuity & Backup Guide

Resilience Strategy for Modern Threats

A backup strategy is the plan for getting the business working again after ransomware, theft, hardware failure or a simple mistake, fast enough that the outage never becomes a crisis. This guide covers the 3-2-1 rule, the gap in Microsoft 365 and Google Workspace, recovery objectives with worked examples, and a restore-test schedule you can adopt as is.

1. What is the 3-2-1 backup rule?

The 3-2-1 rule means keeping three copies of your data, on two different types of storage, with one copy off site. Each number removes a different way of losing everything at once.

3 copies of your dataYour live data (copy 1), a local backup for fast restores (copy 2) and an off-site backup for disasters (copy 3).Why three: any single copy can fail, and two copies kept together tend to fail together. A third copy elsewhere is what survives the bad day.
2 different types of storageNever keep the backup on the same server or disk as the data. A NAS plus cloud storage is the usual pair.Why two: a power surge, a failed RAID controller or one stolen admin password can take out everything on the same system. Different storage means different failure modes.
1 copy off site, and immutableKeep one copy in another building or a cloud data centre, on storage that cannot be changed or deleted until a retention period ends, even by an administrator.Why off site and immutable: fire, flood and theft take out the office and the NAS together, and modern ransomware hunts for backups before it encrypts anything. An immutable copy is the one it cannot reach.

Example: an office running its accounting database on a local server keeps the live database on the server (copy 1), hourly backups on a NAS in the comms cupboard (copy 2), and a nightly immutable copy in cloud storage in another city (copy 3). Many providers now extend the rule to 3-2-1-1-0: one copy offline or immutable, and zero errors in the last restore test.

2. Does cloud sync count as a backup?

No. OneDrive, Google Drive and Dropbox sync every change to every device within seconds, including deletions and files encrypted by ransomware.

Sync keeps files available. A backup keeps them recoverable, by holding copies from before the problem started, somewhere the problem cannot reach. Version history helps with single files, but it is limited in time and an attacker with admin access can delete it.

3. Does Microsoft back up my Microsoft 365 data?

Not in the way most people assume: Microsoft keeps the service running, but recovering deleted or damaged data is your responsibility.

  • Microsoft ensures the infrastructure works (uptime).
  • You are responsible for the data (retention and recovery).
A separate cloud-to-cloud backupUse a third-party tool such as Veeam Backup for Microsoft 365, Acronis or Datto for Exchange Online, SharePoint and OneDrive. Google Workspace needs the same.Why: deleted mailbox items are kept for 14 days by default (30 at most), and the OneDrive and SharePoint recycle bins for 93 days. After that, or after a malicious permanent deletion, the data is gone.

4. What are RPO and RTO?

RPO (recovery point objective) is how much recent data you can afford to lose. RTO (recovery time objective) is how long a system can be down before the damage is serious.

Set both per system, not once for the whole business, because the right target depends on what each system costs you per hour. Tighter targets cost more: a 15-minute RPO needs replication, while a 24-hour RPO needs only a nightly backup job.

Example recovery objectives for a 20 to 50 person office
SystemExample RPOExample RTOWhat that requires
Accounting database1 hour4 hoursHourly backups to a local NAS, a nightly off-site copy and a written restore runbook
Email24 hours2 hours for one mailboxDaily cloud-to-cloud backup with single-item restore
Shared files24 hoursMinutes for a file, 1 day for a whole libraryDaily backup plus version history
On-premises server4 hours8 hoursImage backups that can boot as a virtual machine while the server is repaired
Booking or point-of-sale system15 minutes1 hourReplication or continuous data protection to a standby system

Worked example: the accounting server fails at 15:00 and the last backup ran at 14:00, inside its one-hour RPO, so the finance team re-captures one hour of entries. The restore takes three hours, inside its four-hour RTO, so they are working again by 18:00. If either number had been missed, the backup design, not the staff, needs fixing.

5. Why is a restore test the only proof a backup works?

A restore test is the only proof because backup software reports success when it copies data, not when that data can actually be restored.

Corrupted backup files, expired credentials and missing encryption keys all show up at restore time. Testing on a schedule moves that discovery to a quiet Tuesday instead of the day you need it.

A restore-test schedule
How oftenTestPass when
DailyRead the backup job report and rerun any failed jobEvery job succeeded or was rerun the same day
MonthlyRestore a random file and a random emailBoth open intact, and the time taken is recorded
QuarterlyRestore a whole folder or mailbox, and boot one server backup as a virtual machineDone within the RTO, with data inside the RPO
YearlyFull recovery exercise of a critical system from the off-site copyThe system owner signs off and the runbook is updated
After any big changeRestore test of the changed or new systemThe new system is restorable before it is relied on
Quarterly fire drillPick a random folder, delete it, restore it and time the restore. If it took four hours, ask whether the business can afford to be down for four hours.
Image-based verificationFor servers, check that the backup can boot as a virtual machine (often called instant recovery), so the business can run from the backup while the main server is fixed.

6. What does POPIA expect from backups?

POPIA requires reasonable technical measures to prevent the loss of personal information, and a tested backup is one of the plainest ways to show you took them.

Backups hold the same personal information as the live systems, so they need the same protection: encrypt them, restrict who can restore them, and delete old copies when the retention period ends.

Need this designed and run for you? See backup and disaster recovery, or keep the office online through power cuts with the load shedding IT continuity guide.

Legal Disclaimer: This guide is provided for general informational purposes only and does not constitute professional advice. AMEA Technologies (Pty) Ltd makes no representations or warranties of any kind regarding the completeness, accuracy, or suitability of this information. Any reliance you place on this content is strictly at your own risk. We accept no liability for any loss or damage arising from the use of this guide. You are advised to consult qualified IT professionals before implementing any recommendations.