Robert Edmonds

Resilience

Backup: one isn't enough

Robert Edmonds · November 2026 · 6 min read

Most businesses will tell you they have a backup. In my experience, that isn't enough. When a business is properly hacked, the attackers usually go after the backups too, because a business that can't restore is a business that pays. Good backup means more than one backup, each designed for a different kind of problem.

Different jobs

Backups have more than one job, and one backup rarely does them all well.

1. A daily backup for everyday problems

Start with the information your business couldn't function without. The NCSC's list is a good prompt: your website, emails, invoicing, documents, contacts and customer information. Add line-of-business systems, such as your CRM, case management or stock system, and the settings needed to rebuild them.

Back these up automatically, at least daily, and make sure someone is alerted when a backup fails. A backup that relies on someone remembering will eventually be missed.

2. Microsoft 365 is not a backup

This is the most common misunderstanding I see. Microsoft 365, Google Workspace, OneDrive and Dropbox keep your data available, but they synchronise it. Delete a file, or have it encrypted by ransomware, and that change syncs too. Deleted items are only kept for a limited period, and these services aren't designed to be a full, independent backup of your business.

If your email and documents live in Microsoft 365, they need their own backup, kept with a separate provider and separate login details.

3. A backup the attackers can't reach

This is the backup that protects you against a cyber attack, and it needs two properties:

Protect the backup accounts themselves too. Turn on two-step verification, as the NCSC recommends, and use login details that aren't connected to your day-to-day accounts, so whoever compromises one can't delete the other.

4. Separate your backups from your live systems

There are different types of backup, and a sound setup uses more than one:

Whatever mix you use, the backups must be kept separate from your production systems. A backup on the same network, using the same logins, can be lost in the same incident.

5. Plan for losing a whole site

Cyber attacks aren't the only way to lose everything. A fire, flood or power failure can take out an entire office, server room or data centre. Keep at least one backup in a different location, far enough away that the same event can't affect both. Where your systems are hosted in a data centre, that means a second data centre in a different part of the country.

6. Test that you can restore

Learn how to restore your backups and check they contain everything you need. Go further than restoring one file: find out how long it would take to get the whole business working again from your cyber recovery copy. That number is the one that matters, and it belongs in your recovery plan.

Questions to ask whoever looks after your IT

  • What exactly is backed up, including Microsoft 365 email and documents?
  • How often does it run, and who is told if it fails?
  • Do we have a copy that's air-gapped or can't be overwritten?
  • Is at least one copy in a different location, far enough away to survive a fire or flood?
  • Could someone with our admin passwords delete our backups?
  • When did we last test a full restore, and how long did it take?
  • If we lost everything today, how long until we're working again?

Want a second opinion on your setup?

I help businesses put these basics in place properly and keep them there, as a fractional IT Director or on a defined project.

Email rob@omee.co.uk

More articles