Almost every organisation says "yes, we have backups". Far fewer have ever tried to get their files back. The usual surprises come out at the worst moment: the backup stopped running months ago, it only covered one folder, nobody knows the password, or restoring everything would take a week.

This guide is a simple way to find out where you stand before you need it.

1. List what actually needs protecting

Start with the data, not the backup tool. Write down where your important information lives:

  • Shared drives or a file server
  • Laptops and desktops (especially the desktop and downloads folders people really use)
  • Email
  • Cloud services: Microsoft 365, Google Workspace, accounting and booking systems
  • Websites and their databases
  • Phones, if photos or messages matter for your work

A common mistake is assuming that cloud services back themselves up. Most of them keep your data available, but if a file is deleted or encrypted by mistake, they may only keep it for a limited time. Check what each service promises and whether you need your own copy.

2. Follow the 3-2-1 rule

A simple, well-known rule of thumb:

  • 3 copies of your data (the original and two backups)
  • on 2 different types of storage
  • with 1 copy somewhere else, off-site or in the cloud

On top of that, keep at least one copy that can't be changed or deleted from the normal network, for example an immutable cloud backup or a disk that is disconnected after each backup. Ransomware often tries to destroy the backups first.

3. Check that backups really run

Open the backup software or service and check:

  • When did the last successful backup finish?
  • Are there errors or warnings nobody has looked at?
  • Does it include all the places from your list in step 1?
  • Does someone get an alert when a backup fails?

If nobody gets notified when a backup fails, it can be broken for months without anyone noticing.

4. Do a restore test

This is the step that matters most. Pick a few real files and restore them to a different location:

  • A single document from last week
  • A whole folder from a month ago
  • An email or mailbox, if email is backed up
  • Ideally, once a year, a full computer or server

Then check: do the files open? Are they the right version? How long did it take? Did you need a password or a person who wasn't available?

Write down the result and the date. A short log like "restored the invoices folder from 3 weeks ago, took 10 minutes, worked" is worth a lot when something goes wrong.

5. Decide how much you can afford to lose

Two simple questions help you choose the right setup:

  • How much work can we lose? If backups run once a night, you could lose a day's work. Is that acceptable?
  • How long can we be without it? If restoring everything takes two days, can the business wait two days?

The answers don't need to be perfect. They tell you whether daily backups are enough or whether some systems need more frequent copies and a faster recovery plan.

6. Keep the keys safe

Backups are often encrypted, which is good, but the encryption key or password must be stored somewhere safe outside the system being backed up. Keep the instructions for restoring, the account details for the backup service, and contact details for whoever helps you, somewhere you can reach even if the office computers are down.

7. Make one person responsible

Backups fail quietly when they are "everyone's job". Name one person (or your IT partner) who checks the backup status regularly and runs a restore test every few months. Put the next test date in the calendar.

Summary

  • We know where all our important data lives.
  • We have at least one off-site copy and one that ransomware can't reach.
  • Failed backups trigger an alert.
  • We restored real files in the last three months, and it worked.
  • Restore instructions and keys are stored safely outside the system.
  • One named person is responsible.

If you can't tick all of these, the IT Health Check includes a backup review, and as your IT Support Partner I can run the checks and restore tests for you.