Almost every business says “yes, we have backups.” Far fewer have ever tried to restore from one. The first time you find out whether a backup works is usually the worst possible day: after a ransomware attack, a failed server, or a deleted folder. This post is about making sure that day goes well.
A backup isn’t a backup until you’ve restored it
Backups fail quietly. The job stops running after a password change, and nobody notices. The wrong folders were selected. The backup drive was plugged in the whole time, so ransomware encrypted it too. The one person who knew the password has left. Or the restore works, but takes three days when the business can afford one.
None of that shows up until you test.
The 3-2-1 rule, in plain words
3 copies of your important data: the original and two backups.
2 different kinds of storage, for example the office server and a cloud service, so one type of failure can’t take out both.
1 copy offsite, away from the office. Fire, flood and theft, and in the Philippines typhoons and floods, reach everything in one building.
Many experts now add two more: 1 copy that can’t be changed or deleted (offline or “immutable”), and 0 errors, meaning you tested the restore.
What to back up
Think beyond the shared folder:
File server or NAS
Accounting, billing and point-of-sale data
Databases behind your website or apps, and the website files
Email and documents in Microsoft 365 or Google Workspace
Configuration of the router, firewall and servers
Password manager recovery codes and software license keys
Microsoft 365 and Google Workspace keep deleted items only for a limited time, so treat them as a convenience, not as your backup.
Mistakes we see in small offices
One external drive plugged in all day. Ransomware encrypts it along with everything else.
Backups stored on the same server or NAS as the original data.
Confusing sync with backup. OneDrive or Google Drive sync mirrors changes, including deletions and encrypted files.
Nobody owns it. No one checks that the job ran.
Backup logins shared with the main admin account. If an attacker takes that account, your backups go too.
No offsite copy because it seemed like an extra cost.
Never testing the restore.
A 30-minute restore test
You can do this once a month:
Pick a file at random from about three months ago.
Restore it to a different folder, not on top of the original.
Open it, and check that it’s complete and that it’s the right version.
Write down how long it took and anything that went wrong.
Once a quarter, go further: restore one whole system, such as a database or a server, onto a separate machine, and check that the business application actually works. Once a year, run a “worst day” drill: assume the office is unusable, and see how you would get back up using only your offsite copy.
How fast, and how much loss, can you live with?
Two simple questions decide how often to back up and how:
How much data can we afford to lose? If the answer for your sales system is “no more than an hour,” you need backups at least hourly. This is the recovery point.
How long can we be down? If the answer is “half a day,” a restore that takes three days is a failure. This is the recovery time.
Write the answers down for each important system. Your test results show whether you meet them.
Ransomware and your backups
Attackers know backups are what let you say no to a ransom, so they go after them first. Three habits help:
Keep at least one copy offline or immutable, which can’t be altered even by an admin.
Use separate logins for backups, with extra verification turned on for the cloud account.
Don’t leave a backup share permanently connected to your computers, and set alerts so a failed job reaches a person.
A simple setup that works for a small office
A daily copy to a local device, such as a NAS, for fast restores.
A nightly copy to a cloud service, with versions kept and deletion protection on.
A separate backup for Microsoft 365 or Google Workspace data.
A one-page document: what is backed up, where, who checks it, and how to restore.
A monthly 30-minute restore test, with the date and result written down.
Quick checklist
We know what data matters and where it lives.
We follow 3-2-1, with one copy offsite.
One copy cannot be changed or deleted.
Backup logins are separate and protected.
Someone owns checking the jobs.
We have restored a file this month and a whole system this quarter.
We have written down how long a restore takes.
Want a second pair of eyes?
At Northgate IT Consultancy we review how small businesses protect and recover their data, then fix the gaps. Send us a message at northgate-it.com.ph/contact. A short call is free.
Notes
I kept it vendor-neutral so it stays accurate and doesn’t read like an ad.
I wrote no prices, no client names, and no claims that need a source.
The images and the short Facebook version are next. Want me to make them? After that, the infrastructure series can continue with ransomware (the first hour), the Microsoft 365 settings, and the office NAS.