Backup Solutions in Rwanda
Backup design and testing so a restore actually works when you need one, not just when you test it.
Backup solutions make sure you can get your data back after anything from a deleted file to ransomware or a fire, by keeping several copies in different places, at least one of which can’t be altered, and by testing restores on a schedule. Any organisation that hasn’t restored from its backups recently, or isn’t sure where they all are, needs it. This page covers backup and recovery of data. Keeping the organisation working while systems are recovered is covered by business continuity planning.
What is a backup solution, and who needs it
It’s the design, setup and testing of how your data is copied, where the copies are kept, how long they’re retained and how quickly each system can be restored. It covers servers, virtual machines, file storage, databases, and where relevant, Microsoft 365 and laptops. Every organisation needs it; those holding financial, health, client or personal data need it most.
The problem it solves
Most backup failures are discovered during a restore. The job had been failing for months, the backup sat on the same server that died, ransomware encrypted the backup along with everything else, or retention was so short that every copy already contained the problem. A designed and tested backup replaces those assumptions with evidence that each system can be brought back.
The 3-2-1 rule, and why ransomware changed it
The long-standing rule is simple: keep three copies of your data, on two different types of storage, with one copy off site. It protects against hardware failure and disasters at a single site.
Ransomware changed the threat. Attackers who gain administrator access deliberately look for backups and delete or encrypt them before demanding payment. So modern designs add:
- One copy that can’t be altered or deleted for a set period, through immutable storage, an offline disk or a cloud store with object lock, protected by credentials separate from your main network.
- Zero errors on verification: restores tested and confirmed, not just backup jobs completed.
That’s often summarised as 3-2-1-1-0. We design to it, scaled to what each system is worth.
Two numbers for every system
How much data can you afford to lose? This sets how often backups run, from once a night to every few minutes.
How long can you be without it? This sets the restore method: a simple restore, a standby copy ready to start, or replication to another site or the cloud.
We agree both per system, then design, and the cost follows from the answers.
What the work involves
- Inventory systems and data, and agree the two numbers for each.
- Design frequency, locations, the immutable copy, retention and encryption.
- Set up backup software, local and off-site storage, and separate backup credentials.
- Run a full restore test of each critical system, and record how long it took.
- Document restore procedures for each system.
- Monitor and retest on a schedule, at least quarterly for critical systems.
What’s included and what’s not
Included: backup design, configuration of local and off-site copies, an immutable or offline copy, restore testing, and written procedures.
Not included unless bundled: the storage hardware itself (see storage solutions), the wider continuity plan (see business continuity) and ongoing cloud storage charges for off-site copies, which are billed by the provider.
Typical timelines and what drives cost
Design and setup typically take two to four days, including the first full restore test. Cost is driven by data volume, the number of systems, how often backups run, how long copies are kept, off-site and cloud storage, immutability, and how frequently restores are tested. The first full copy to the cloud can take days over a modest connection, so it’s often seeded locally first.
Equipment typically used
Backup software suited to your servers and virtualisation platform, a local backup appliance or NAS with immutability, cloud storage with object lock or a rotated offline disk, Microsoft 365 backup where needed, and monitoring that alerts on any failed job.
Common mistakes we see
Backups stored on the same server or network as the data. Backup credentials the same as everyday administrator accounts. No copy that ransomware can’t reach. RAID or file sync mistaken for backup. Retention of only a few days. Failed jobs reported by email to nobody. And no restore ever tested.
.DXzPgUuV_2myRml.webp)
Servers & Systems
Related services
-
Server Room Infrastructure
Power, cooling and rack infrastructure built around the servers it needs to support.
-
System Monitoring
Alerting on the metrics that predict failure, not just a dashboard nobody watches.
-
Business Continuity
A continuity plan for what happens when a server, site or connection goes down.
Insights
Related reading
-
.Bty1UFki_ZFLEIL.webp)
, 4 min read
Common Backup Mistakes Rwandan Businesses Make
A handful of specific mistakes recur in how businesses approach backup — here's what they are and why each one leaves data less protected than it seems.
-
.C49RFZUn_Z1F8CW2.webp)
, 4 min read
How Much Does a Backup Solution Cost in Rwanda?
Backup solution cost depends on data volume, retention period, and restoration testing — here's what drives the number for a genuinely reliable setup.
Frequently asked questions
How do we know our current backups actually work?
Only by restoring from them. A backup job can report success while missing folders, skipping open databases or saving corrupted data. We restore real files, whole virtual servers and application databases to a test location on a schedule, check they open and work, and record the time each restore took. That record is your proof, not the green tick on the job.
How often should backups run?
As often as the data you could lose is worth. If losing a day of entries in the accounting system is unacceptable, nightly backups aren't enough, and that system may need hourly backups or continuous replication. File shares that change slowly might be fine overnight. We set frequency per system from the data loss you agree you can tolerate.
Should backups be stored locally, in the cloud, or both?
Both, in most cases. A local copy restores quickly after an everyday problem, such as a deleted folder or a failed server. An off-site or cloud copy survives fire, theft or a building-wide failure that would destroy anything kept on site. At least one copy should also be immutable or offline, so ransomware with administrator access can't delete it.
How long are backups kept before being overwritten?
Long enough to recover from problems discovered late. Many incidents, such as a corrupted file or a quiet intrusion, are found weeks after they start, so keeping only a few days of backups can mean every copy is already affected. A common pattern is daily copies for a month, monthly copies for a year, and longer for records you're required to keep.
What's involved in actually restoring from backup if we need to?
A written procedure for each system: where the backup is, who can access it, what order to restore in, and how long it should take. For a deleted file it's minutes. For a whole server it can be hours, and restoring it to new hardware or the cloud may need extra steps. We practise the procedure with you so it isn't followed for the first time during an emergency.
Do we need to back up Microsoft 365?
It's worth considering. Microsoft keeps the service running and holds deleted items for limited periods, but it isn't designed as a long-term backup of your data against accidental deletion, a malicious insider or a compromised account. A third-party Microsoft 365 backup keeps independent copies of mailboxes, OneDrive, SharePoint and Teams for as long as you choose.
What happens if your server fails tomorrow?
Tell us what you run and how it’s backed up. We’ll assess the risk and quote a fix sized to it.