Backup & Disaster Recovery Uganda: Test Before You Need It

Most businesses we visit can tell us they have a backup. Far fewer can tell us when they last restored from it. That gap is where data gets lost.

A backup that has never been tested is a hope, not a plan. This guide explains how to build a backup and disaster recovery setup that suits Ugandan conditions, and how to prove it works before a bad day arrives.

Why backups fail when you need them most

When we are called in after a data loss, the cause is rarely exotic. It is usually one of these:

• The backup job stopped weeks ago and nobody noticed.
• The backup drive sits in the same room, plugged into the same socket, as the server it protects.
• The only copy of the data lives on one laptop or one server.
• Backups were never restored as a test, so nobody knew a folder was missing or the files were corrupt.
• Ransomware encrypted the backup too, because it was a shared drive the infected computer could reach.
• The person who set it up left, and nobody has the passwords.

Every item on that list is preventable, and none of them requires an expensive system.

Know your two numbers: RPO and RTO

Before choosing any tool, decide two things. They sound technical, but the ideas are simple.

Recovery Point Objective (RPO) is how much data you can afford to lose, measured in time. If you back up once a night and the server fails at 4pm, you lose a day's work. If that is unacceptable, you need more frequent backups.

Recovery Time Objective (RTO) is how long you can afford to be down. If your tills, bookings or invoicing stop while you wait for a restore, how many hours can you survive?

Answer these per system, because they are rarely the same for everything:

These are examples only. Your own numbers should come from how your business actually operates.

The 3-2-1 rule, plus one

The standard rule of thumb is simple:

• 3 copies of your data (the original plus two backups).
• 2 different types of storage (for example a NAS and cloud storage).
• 1 copy offsite, away from your premises.

We add a fourth point: keep at least one copy immutable or offline. Immutable means the backup cannot be changed or deleted for a set period, even by someone with an admin password. This is what saves you when ransomware reaches your network or a staff account is compromised.

A practical setup for a small or mid-sized office looks like this:

1. Working data on your server or workstations.
2. A local backup to a Synology NAS for fast restores of individual files and full servers.
3. An encrypted, immutable copy in the cloud for protection against theft, fire, flood and ransomware.

Risks specific to Ugandan businesses

Generic advice from overseas often ignores local conditions. These are the ones we plan around.

Power instability. Surges and sudden cuts can corrupt drives and interrupt backup jobs halfway through. A properly sized UPS on your server and NAS lets them shut down cleanly. See our guides on UPS systems for server rooms and surge protection.

Theft and break-ins. If your backup drive is in the same office as the server, one theft takes both. Offsite copies are not optional.

Limited or costly upload bandwidth. Cloud backup depends on upload speed. The first full backup can take days over a slow link, so we schedule it overnight, back up only what matters first, and use incremental backups afterwards so only changes are sent. For very large datasets, an initial seed from a local copy can help.

Water, fire and building issues. Small offices often keep equipment on the floor or in a cupboard. Raise racks, avoid areas with leaks, and keep one copy outside the building.

Staff turnover. Document who owns the backups, where credentials are stored, and who can restore. A backup only one person understands is a risk.

What you should be backing up

Many businesses back up documents and forget the rest. Check this list:

• Shared files and staff documents
• Accounting, payroll and ERP data
• POS databases and configuration
• Email (including cloud mailboxes, which are not automatically backed up for you)
• Server configurations and virtual machines
• Network device configurations (switches, firewalls, Wi-Fi controllers)
• CCTV and access control databases, where you depend on them
• Laptops of key staff, especially finance and management

If losing it would stop your business or cost you money, it belongs on the list.

How to test your backup: a simple restore drill

This is the step most businesses skip, and it is the one that matters most.

Monthly: restore a few random files. Pick files from different folders and dates and restore them to a temporary location. Open them and confirm they are complete.

Quarterly: restore a full system. Restore a server, database or virtual machine to a spare machine or test environment. Time it. That time is your real RTO, and it is often longer than people assume.

Yearly: run a disaster scenario. Pretend the office is unavailable. Can you get the business running from the cloud copy and a few laptops? Who does what? Write it down.

After every test, record the date, what was restored, how long it took, and anything that failed. Fix what failed and test again.

A quick checklist:

• Backup jobs report success daily, and someone reads the report
• Alerts go to a monitored email or phone, not a former employee
• Restore tested within the last 30 days
• One copy is offsite
• One copy is immutable or offline
• Backup credentials are stored securely and separately from everyday admin accounts
• A written recovery plan exists and staff know where to find it

Backups and ransomware

Modern ransomware looks for backups before it encrypts anything. To protect yours:

• Do not leave backup shares mapped as normal drives on staff computers.
• Use separate credentials for backup systems, with multi-factor authentication turned on.
• Keep an immutable or offline copy that an attacker cannot delete.
• Keep endpoints protected and patched. Our ransomware protection guide covers prevention and recovery in more detail.

Sample plan for a 20-person office

This is an illustration, not a quote. Real designs depend on your data size, systems and budget.

Common mistakes to avoid

• Treating a USB drive in a drawer as a backup strategy
• Backing up to the same device or room as the original
• Assuming cloud email and file sync services are backups
• Never checking backup reports
• Never testing a restore
• Having no written plan for who does what

Get a backup plan you can trust

Backspace designs, installs and monitors backup and recovery systems alongside the power, network and server infrastructure they depend on. A free site assessment will show where your data is exposed today and what a sensible fix looks like.

Book a free site assessment or call +256 786 394 913.