Backup you have actually restored from.
We back up servers, laptops and Microsoft 365 to immutable off-site storage, then test restores on a schedule and give you the evidence, so you find out it works before you need it to.
- Protects
- Servers, laptops, Microsoft 365
- Storage
- UK data centres
- Ransomware
- Immutable copies
- Restore tests
- Scheduled, evidenced
- Encryption
- AES-256
Three assumptions that cost businesses everything.
“It’s in the cloud, so it’s backed up”
Microsoft protect their platform, not your content. A deleted mailbox, an encrypted SharePoint library or a leaver clearing their OneDrive are your responsibility once retention runs out. Why Microsoft 365 needs its own backup.
“The backup runs every night”
Running is not the same as working. We regularly inherit backups that have been failing silently for months, or copying to a drive sitting next to the server it protects.
“We could restore it if we had to”
Restoring one file takes minutes. Rebuilding a server with no plan can take days. Almost nobody knows their real recovery time until they need it.
Several copies, one of which an attacker can’t touch.
Ransomware looks for backups first. The defence is a copy held off-site that can’t be altered or deleted for a set period, not even with your own administrator password.
Local copy
On-site storage for fast everyday restores. A deleted folder back in minutes.
FastOff-site copy
Replicated to UK data centres and encrypted, so a fire, flood or theft doesn’t take the backup with it.
Off-siteImmutable copy
Held in a write-once state for a defined period. A compromised admin account can’t delete or encrypt it.
LockedTested restores
Recovery points restored on a schedule, with the evidence attached to your account.
Verified
What we protect.
Servers
Image-level backup of physical and virtual servers, so a full rebuild onto new hardware or into the cloud is possible.
Microsoft 365
Exchange Online, SharePoint, OneDrive and Teams backed up independently, with point-in-time restores and unlimited storage.
Laptops and desktops
Endpoint backup for people who keep work locally, which, whatever the policy says, is most of them.
Databases
Application-aware backup for line-of-business databases, so restores come back consistent.
Disaster recovery
For critical systems, the backup can run as a virtual machine in the cloud while the original is repaired.
Monitoring
Every job monitored. A failure becomes a ticket the same morning, not a surprise months later.
Agree two numbers before anything goes wrong.
Every backup design trades cost against speed. We set these per system with you rather than applying one policy to everything.
Recovery point: how much work you could afford to lose. Hourly for a busy database, nightly for an archive.
Recovery time: how long you could afford to be down. Some systems justify instant failover. Others can wait a day.
| System | Backup frequency | Recovery target |
|---|---|---|
| Line-of-business server | Hourly | Under 1 hour |
| File shares and SharePoint | Every 4 hours | Same working day |
| Microsoft 365 mailboxes | Several times a day | Same working day |
| Laptops | Daily | Next working day |
| Loss of the whole site | n/a | Agreed in your recovery plan |
Example schedule. Yours is set per system during onboarding.
Questions we get asked
What is an immutable backup?
An immutable backup is a copy that cannot be changed or deleted for a set period, even by someone with administrator access. It is the main defence against ransomware, which tries to destroy backups before encrypting live data.
Where is our data stored?
In UK data centres, encrypted in transit and at rest. We can confirm locations in writing for your data protection records.
How quickly could we get a whole server back?
With local storage in place, a virtual copy can usually be running within the hour while the original is rebuilt. Without it, it depends on data volume and connection speed, which is exactly why we agree the target in advance.
Do you test the backups or just monitor them?
Both. Monitoring catches failed jobs the same morning. Testing means actually restoring, booting a recovered server and opening recovered files, on a schedule, with the evidence kept.
We already have a backup product. Do we have to change?
Not necessarily. We will review it first. Sometimes the product is fine and the configuration is the problem.
Related services
When did you last test a restore?
If the honest answer is never, that is the conversation to have. We will show you what is protected, what isn’t, and how long recovery would really take.