DISASTER RECOVERY · BUSINESS CONTINUITY

When it all goes down, how fast do you come back?.

Ransomware, a dead server, a flooded office, a deleted database — the question isn't whether something takes you down, it's how long you're down when it does. I build the plan that turns a catastrophe into a few hours of disruption instead of a few weeks of survival mode.

A backup you've never tested is just a hope. I deal in plans that actually work.

Most small businesses think they're covered because something is "backing up." Then the bad day comes and they discover the backup was incomplete, encrypted along with everything else, or impossible to restore in time. Here's what real recovery looks like.

A number you can put on it
How much data you can afford to lose and how fast you must be back — defined, agreed, and engineered for. Not guessed at after the fact.
Backups that survive the attack
Air-gapped, immutable copies that ransomware can't reach — because a backup sitting on the same network it's protecting isn't a backup.
A plan you've rehearsed
A written runbook for who does what when systems are dark, tested before you need it — so recovery is a procedure, not an improvisation.

Most "backup" setups fail the only test that matters.

The day you need to restore is the worst day to find out it doesn't work. Three ways it goes wrong for businesses your size:

01

The backup got encrypted too

Modern ransomware hunts for your backups first. If they live on the same network, the attacker takes them out before you even know you're hit.

02

Nobody ever tested a restore

Backups run green for years and no one confirms they can actually be restored. A backup you haven't restored from is an untested assumption, not a safety net.

03

There's no plan, just people

When it goes down, everyone turns to one person who's improvising under pressure. That's not continuity — that's a single point of failure with a pulse.

I've brought a business back from ransomware in two hours. Most never recover that fast.

I'm not selling you a backup product. I've stood in the middle of a live attack and walked a multi-site business back from it.

Two hours, because the plan was real

In 2020 ransomware hit a business I ran IT for. We were back in two hours instead of the weeks most firms lose — because the backups were air-gapped and the recovery plan had been built and tested before we needed it.

Multi-site, multi-state experience

I've run continuity across seven locations in five states. I know what breaks when a business has more than one place to keep running — and how to keep all of them up.

Continuity leadership, not a box of tapes.

I own the plan and hold your vendors to it. You contract the backup and infrastructure providers directly — I make sure what they deliver actually protects you.

Recovery objectives & risk review

We define how much downtime and data loss the business can actually absorb, then design backward from those numbers instead of hoping the current setup is enough.

Backup architecture review

I assess what you have against what ransomware and hardware failure will actually do to it — and specify the air-gapped, tested setup that holds up.

Incident & recovery runbook

A written, rehearsed plan for the first hours of an outage: who acts, what gets restored first, who gets called, and how the business keeps moving meanwhile.

Tested restores, not assumptions

I make sure restores are actually performed and verified on a schedule — so "we're backed up" is a proven fact, not a comforting story.

The time to plan for downtime is before it happens.

Let's make sure a bad day stays a bad day — not a closed business.

grey@okcvcio.com · (405) 209-6071 · okcvcio.com