Most businesses have some kind of backup. Far fewer know whether it actually works. A backup that has never been tested is a hope, not a plan. This guide explains why disaster recovery testing matters, why Microsoft 365 needs its own backup, and how often you should test.
Why disaster recovery testing matters
When something goes wrong, whether it is ransomware, a failed server, a deleted mailbox or a fire, you want to know exactly how long recovery will take and what you will get back. Testing finds the problems while the stakes are low: corrupted backups, missing data, expired credentials, restore steps nobody has documented, and recovery times far longer than the business can tolerate.
Microsoft 365: the hidden need for backup
Many organisations assume Microsoft backs up everything in Microsoft 365. Microsoft keeps the service running, but it works on a shared responsibility model: you are responsible for your data. Built-in protections are limited. Deleted items in SharePoint and OneDrive sit in recycle bins for a set period, and Exchange Online keeps deleted mail for a short window. They are not designed to protect you against ransomware, malicious deletion, accidental overwrites or an account that has been compromised.
A dedicated Microsoft 365 backup keeps independent copies of email, files, Teams data and more, so you can restore what you need, to a point in time, even long after the built-in retention has expired.
On-premises systems still matter
Many businesses still run local servers for line-of-business software, file shares or databases. These need regular backups to separate storage, ideally including an offsite or cloud copy, following the 3-2-1 rule: three copies of your data, on two different types of storage, with one copy offsite. Add an offline or immutable copy to protect against ransomware.
Benefits of regular testing
- Confidence that your data can really be restored.
- Known recovery times, so you can plan around them.
- Documented, rehearsed steps that staff can follow under pressure.
- Early warning of failing storage, expired licences or broken jobs.
- Evidence for insurers, auditors and clients that you take resilience seriously.
How often should you test?
As a guide, run a simple restore test of a file or mailbox monthly, test restoring critical systems at least twice a year, and run a full disaster recovery exercise at least once a year or after any major change. Critical systems and regulated industries may need to test more often.
What a good test includes
- Pick the systems and the scenario, such as a server failure or ransomware.
- Define your recovery time objective (how fast) and recovery point objective (how much data loss is acceptable).
- Restore to an isolated environment and verify the data and applications actually work.
- Record how long it took and what went wrong.
- Fix the gaps and update the plan.
Final thoughts
Key takeaways
- A backup that has never been tested is a hope, not a plan.
- Microsoft keeps the service running, but you are responsible for your data under the shared responsibility model.
- Built-in protections such as recycle bins are limited, so Microsoft 365 needs its own independent backup.
- Testing finds problems while the stakes are low, including corrupted backups, missing data and recovery times that are too long.
Disaster recovery testing: frequently asked questions
Does Microsoft back up my Microsoft 365 data?
Microsoft keeps the service running, but it works on a shared responsibility model, so you are responsible for your data. Deleted items sit in recycle bins for a set period and Exchange Online keeps deleted mail for a short window. That is not designed to protect against ransomware, malicious deletion or a compromised account.
What does disaster recovery testing find?
It finds corrupted backups, missing data, expired credentials, restore steps nobody has documented, and recovery times far longer than the business can tolerate.
What events should our backups protect against?
Ransomware, a failed server, a deleted mailbox and a fire are common examples. Knowing exactly how long recovery will take and what you will get back is the point of testing.
Related reading: Cloud backup and recovery and Disaster recovery and business continuity.
Backup is only half the job. Testing is what turns copies into confidence. Total Solutions IT provides managed backup for Microsoft 365 and on-premises systems, including regular restore testing. Call 02 6061 4222 to talk about protecting your data.


