
Business Continuity & Backup Guide
Resilience Strategy for Modern Threats
A backup strategy is the plan for recovering business operations fast enough to survive ransomware, theft and human error; it is about restoring the business, not just saving files.
1. What is the 3-2-1 backup rule?
Any strategy less than this is a gamble, not a backup.
3 Copies of DataYour live data (Copy 1), a local backup for speed (Copy 2), and a cloud backup for disaster (Copy 3).
2 Different Media TypesDon't store backups on the same server as the data. If the power supply kills the server, it kills the backup too. Use NAS + Cloud.
1 Copy Offsite (Immutable)This is critical for ransomware protection. Immutable storage means "Write Once, Read Many". Even if a hacker gets your admin password, they scientifically cannot delete the immutable backup until the timer expires.
2. What is the shared responsibility gap?
There is a dangerous myth that "Microsoft backs up my emails". They don't.
- Microsoft ensures the infrastructure works (Uptime).
- You are responsible for the data (Retention).
SaaS Backup SolutionYou MUST use a third-party tool (e.g., SkyKick, Datto, Veeam) to backup Exchange Online, SharePoint, and OneDrive. Microsoft's native recycle bin is temporary (30 days) and does not protect against malicious permanent deletion.
3. Why is a restore test the only proof a backup works?
A backup is Schrödinger's Cat: it both works and doesn't work until you observe it.
Quarterly Fire DrillPick a random folder. Delete it. Try to restore it. Measure how long it took. If it took 4 hours, can the business afford to be down for 4 hours?
Image-Based VerificationFor servers, can you spin up the backup as a virtual machine in the cloud? (Instant Boot). This allows you to work off the backup while the main server is being fixed.
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.
Written and reviewed by the AMEA Technologies engineering team in Johannesburg. Last updated .