Skip to content

01 Services / 01.4 Backup

For: IT department of oneIT team

A green checkmark in the backup console isn't a restore.

We work with the admin who runs the jobs to design and execute a real restoration test, validate immutability, and map the ransomware blast radius so you know what's actually recoverable.

1.1If you run the backups

What you're dealing with

  • Jobs report “Success,” but a full restore hasn't been tested recently.
  • You're not sure an attacker with admin credentials couldn't delete the backups too.
  • Microsoft 365 retention is being treated as a backup.
  • The insurance form asks about immutable or offline copies and you want the answer to be true.

1.2If you sign off on the budget

What you need to know

  • How long the business would actually be down after ransomware.
  • Whether your cyber insurance answers match what's deployed. A wrong yes can put coverage at risk.
  • What RPO and RTO the business can actually live with.
  • What closing the gap would take, in writing.

2.020-minute checklist

Restore readiness checklist

A preview of what's inside. Your admin can run it this week:

  • Have you restored a full system, not just a file, from backup in the last year?
  • Did you record how long that restore took, from start until users could work?
  • Is at least one copy of your backups offline or immutable?
  • Is MFA required to sign in to the backup system and to delete backups or change retention?
  • Is retention long enough to roll back to a point before a problem started, even if it went unnoticed for weeks?
  • Has leadership agreed in writing how much data loss (RPO) and downtime (RTO) is acceptable for each critical system?

Want it in front of leadership? We'll turn your results into a one-page summary.

3.0How an engagement runs

Six steps. No surprises.

  1. 01 · Scoping Call · 30 min · No chargeTell us what you're deciding.We tell you if we can help and what it would take to solve it. If we're not the right fit, we say so.
  2. 02 · Your Proposal · After the CallFixed scope. Fixed price.You get it in writing. Exactly what we'll do and what it costs, agreed before any work starts. No surprise invoices.
  3. 03 · Discovery · Week 1Read the contracts, the stack, the reality.We read the contracts you've been asked to sign, the stack you've already got, and the team's real-world pain points.
  4. 04 · Recommendation · Week 2-3A short, written recommendation.No slide deck theater. You know what to do and why, in writing, in plain language.
  5. 05 · Sourcing & Negotiation · If You Want ItCompetitive process across 250+ providers.If the fix means buying something, we quote at least two options across our provider network. You see every quote, we tell you which ones pay us a commission, and we stay your point of contact through support.
  6. 06 · Implementation Oversight · If You Want ItWe stay through cutover.If the vendor under-delivers, we're the ones calling them. You stay focused on running the business.

4.0Straight answers

The questions your team will ask.

Will you replace our backup vendor or MSP?

Only if the evidence points there. Often the fix is configuration, testing and contract terms.

Do you get paid if we buy through you?

Yes. The provider pays us a commission. We don't add a markup, you'll always see at least two options with pricing, and we stay your point of contact with the provider.

When did you last successfully restore from backup?

Not run a backup job. Actually restore data. If you're not sure, that's the place to start.

Ready to test a restore for real?

The first conversation is free.