Make sure you
can recover.

Backups that aren't tested. Recovery plans that live in someone's inbox. Microsoft 365 that everyone assumes is backing itself up. I help businesses fix those assumptions before they're tested for real.

Backup, recovery,
and a plan.

Microsoft 365 backup

  • Microsoft 365 doesn't back itself up: most businesses assume it does. It doesn't.
  • Mailbox, SharePoint, OneDrive and Teams protected with proper third-party backup (Veeam, Acronis, Keepit or similar).
  • Restore testing: not just the backup running, but an actual restore proven to work.
  • Retention that fits your industry: finance, trust and healthcare often need years, not months.

Server and file backup

  • On-prem servers: proper image-level backup with offsite copies, not just a NAS in the cupboard.
  • Cloud-to-cloud backup for Google Workspace, Dropbox, Salesforce and the SaaS that matters.
  • Endpoint backup for laptops that hold work people shouldn't be losing.
  • Backup monitoring: someone watching the job that didn't run last night.

Business continuity plans

  • A written BCP: short, honest, and actually usable when the WiFi is down and the panic is up.
  • Recovery time objectives agreed with you. How long can you be down, realistically?
  • Run books for the handful of scenarios you're most likely to hit.
  • ISO 27001 and regulator-friendly documentation where your industry needs it.

Ransomware readiness

  • Immutable backups so attackers can't encrypt the only copy of your data.
  • Recovery rehearsals: at least one person who has actually restored something from scratch.
  • Incident response linkage: BCP and incident response planning should be one thing, not two documents.
  • Cyber insurance prep: meeting the controls insurers now quietly require before they'll pay out.

The best time was last year.

The second-best time is a two-week engagement that gives you tested backup, a short written BCP, and one less thing to lose sleep over.

Start a conversation