Loopback designs backup against the failures that actually happen: ransomware encryption, accidental deletion, failed disks, and buildings that flood. We follow the 3-2-1 standard: three copies, two different media, one off-site. Advanced plans include complete user backup across email, workstation, and mobile.
The problem
A backup that has never been restored is a rumour. USB drives in a drawer and a single cloud sync folder both fail the first real disaster.
The outcome
Tested recovery paths, reduced downtime, and a story you can tell a regulator or a client after an incident.
3-2-1 as the floor
Three copies of data, on at least two kinds of media, with one copy off-site. That is the industry standard because the alternatives keep failing.
Ransomware-aware copies
Backups that live only on the same network the malware just encrypted are not backups. Isolation and immutability matter.
Restore, not just replicate
We care about time-to-restore for mailboxes, files, and machines — the metric that decides whether Monday is possible.
Compliance and duty of care
If you hold client or patient data, backup is not IT preference. It is part of staying in business after a bad day.
Questions
Is Microsoft 365 already backed up?
Retention in Microsoft 365 is not the same as a backup you control. Recycle bins empty. Retention policies get mis-set. We back up the workloads that would hurt if they vanished.
How often do you test restores?
Restores are part of the service, not an annual surprise. Frequency is set in the plan so you are not discovering a broken backup during an outage.