Plans & pricing
Client portalGet a quote
Backup and recovery

The backup you never check is the one that isn't running.

Almost every business has backup of some kind. Far fewer know when it last succeeded, how far back it goes, or whether anyone has tried restoring from it. Those three questions are the difference between an outage and a closure — and they're only answerable if somebody is watching.

Endpoint and server backup

Laptops, desktops and servers, backed up on a schedule that matches how quickly the work changes. A file server people write to all day needs a different plan from a laptop that mostly holds email.

  • Windows, macOS and Linux on the same system
  • Full machine images, so a dead server comes back as a machine rather than a pile of files
  • Databases and running applications backed up without stopping them
  • Schedules that fit the working day rather than fighting it

Offsite and cloud copies

A backup sitting on a NAS in the same cupboard as the server is not a backup — fire, flood and theft take both. Copies go offsite, and the storage is yours: your cloud account, your data, no lock-in to a vendor who owns your only copy.

  • Local copy for speed, offsite copy for survival
  • Your own cloud storage, not a black box you can't get data out of
  • Encrypted before it leaves the building, with keys you hold
  • Retention set to how far back you'd realistically need to reach

Ransomware protection

Modern ransomware looks for backups first, because encrypting those is what turns an incident into a payment. Immutable copies can't be altered or deleted for a set period — not by an attacker, not by malware, not by an administrator account that's been compromised.

  • Immutable backups that can't be encrypted or deleted once written
  • Separate credentials, so compromising the network doesn't compromise the backups
  • Alerts on unusual change rates, which is often the first sign
  • A copy that survives even if everything on site is lost

Restore testing and recovery

Backup is the easy half. The question that matters is how long it takes to be working again — and the only way to know is to have done it before the day you need to.

  • Test restores, so recovery is something we've practised rather than assumed
  • Bare-metal recovery to different hardware when the original is gone
  • Recovery to a virtual machine while replacement hardware is on order
  • A written recovery order: what comes back first, and who to call
What we install

We run MSP360 Managed Backup. It backs up to storage you own rather than ours, supports immutable copies against ransomware, and reports every job centrally — which is what lets us notice a failure the morning it happens instead of the day you need the file. Your backup status appears in your HeMi portal, so you can see it too.

Common questions

How far back can we go?

As far as you need — retention is a storage decision, not a fixed limit. We'll size it against what you'd realistically have to reach for and show you the cost difference.

What if we already have backup?

We'll look at what's running and tell you honestly whether it's fine. Sometimes the answer is that it works and just isn't monitored.

How quickly could we be working again?

That depends on what broke and what we've prepared for. It's the right question to ask before an outage, and it's the first thing a site walk covers.

The rest of the stack

One team for all four systems.

Most sites need more than one of these, and they work better when the same team designs them together.