One of the questions I often ask people is:
If your main server failed this afternoon, would you know exactly where all of your data lives?
Nearly everyone says yes.
Then we spend five minutes talking about it, and that's normally when the answer changes…
Because most businesses don't keep everything in one place anymore.
Some files live on the server, others are in Microsoft 365.
Someone has a project saved on their laptop, another department stores documents somewhere completely different because it made sense at the time.
None of that's unusual.
In fact, it's how most businesses naturally evolve.
The problem is that every time data moves somewhere new, someone has to ask a simple question:
Is this actually being backed up?
Quite often, nobody does.
Backups Aren't Just About Hardware Failure
When people think about backups, they usually imagine a server failing. Or perhaps someone spilling coffee over a laptop.
Those things happen.
But they're not the only reason backups exist.
One conversation with a client recently reminded me of that…
They discovered that somebody inside their own business had been doing something they shouldn't.
Much of the evidence was sitting in emails.
Those emails had been backed up automatically for months.
The person involved knew where the backups were stored and tried to delete them.
Fortunately, the backup system had been designed properly.
Deleting an email wasn't enough to remove it completely.
It was still retained, protected by multiple layers of permissions and retention policies.
When the business needed that information, it was still there.
That's the sort of situation nobody plans for.
But it's exactly why a proper backup strategy matters.
Microsoft 365 Isn't Automatically a Backup
This is probably one of the biggest misconceptions we come across…
A lot of people assume that because their email is stored in Microsoft 365, it's automatically protected forever.
It isn't.
If emails are deleted, encrypted by ransomware, or affected by account issues, simply existing inside Microsoft 365 doesn't necessarily mean they're recoverable in the way many businesses expect.
That's why independent Microsoft 365 backups have become so important.
Your production environment and your backup shouldn't be the same thing.
A backup should be a separate, recoverable copy that you control.
The Question Most Businesses Never Ask
Here's another question:
When was the last time you restored something from your backup?
Not checked whether the software says it's running.
Actually restored a file. Or an email. Or a folder.
Because having backups is one thing.
Knowing they'll work when you need them is something else entirely.
Testing restores is just as important as taking backups in the first place.
Otherwise, you're relying on hope. And that isn't much of a disaster recovery plan.
A Good Backup Strategy Works With Minimal Work
The best backup systems aren't the ones with the most features...
They're the ones you barely have to think about so you can get on with whatever you're supposed to be doing.
That means:
– Backing up all the places your business stores data.
– Protecting Microsoft 365 alongside your servers.
– Using sensible retention policies.
– Restricting who can modify or delete backups.
– Regularly testing restores.
– Making sure someone is actually monitoring the whole process.
When all of that happens consistently, backups stop being something you worry about.
They're simply another part of keeping your business running.
The Real Purpose of Business Backup Solutions
Most people think backups exist for the day a hard drive fails.
Sometimes that's true.
But just as often, they're protecting businesses from accidental deletion, ransomware, human error, or situations nobody could have predicted.
The important thing isn't whether you have backup software installed.
It's whether you'd be confident relying on it if tomorrow turned into one of those days.
If you're not completely sure where all of your business data is, how it's backed up, or whether those backups have ever been tested, it's probably worth asking the question now rather than after something goes wrong.
Reader Interactions