BRITECITY
Can you open
tomorrow?
Backup & Disaster Recovery · What executives need to know
Make IT Easy
Today’s Agenda
What we’ll cover
- 01
The Business Problem
What downtime really costs, beyond IT tickets
- 02
How Businesses Stop
Ransomware, hardware, people, facilities, and the cloud
- 03
Backup ≠ Recovery
Why “we have backups” is not a plan
- 04
Two Numbers That Matter
How long you’re offline, and how much work you lose
- 05
What Good Looks Like
A simple checklist leadership can own
The Business Problem
When systems stop, the business stops
Revenue freezes
Orders stop. Invoices don’t go out. Appointments can’t be booked. Cash flow doesn’t wait for IT.
Clients lose trust
Missed deadlines, unanswered calls, and “our systems are down” erode confidence faster than a competitor’s pitch.
People sit idle
Payroll still runs. Productivity doesn’t. Every hour offline multiplies across the whole team.
Liability grows
Contracts, insurers, and regulators ask one question after an outage: did you take reasonable steps to recover?
Common Assumptions
What “we’re covered” often means
“We have Microsoft 365 / the cloud.”
Cloud apps protect uptime of the service, not your accidental deletes, ransomware, or a compromised mailbox. That’s retention, not recovery.
“IT said the backup is running.”
A job that finishes is not proof you can restore. Untested backups fail at the worst possible moment.
“We’re small. We’re not a target.”
Attackers automate. Size is not a filter. Many smaller firms are easier because defenses are thinner.
“We’ll figure it out if something happens.”
During an outage, every hour of decision-making is an hour offline. Plans written under stress are not plans.
How Businesses Stop
Six ways operations grind to a halt
Files encrypted. Systems locked. Attackers often try to destroy backups first so you have no clean way back.
Servers and drives age out. One failed disk can take a whole line of business offline without a tested path back.
Deleted folders, bad overwrites, a “cleanup” gone wrong. Most data loss is accidental, and permanent without point-in-time recovery.
Fire, flood, power loss, break-in, wildfire smoke. Anything that only lives in one building can leave with that building.
A retention policy changed. A sync folder emptied. A tenant setting flipped. Quiet failures that only show up at restore time.
Only one person knows how recovery works. If they’re unavailable, the plan is unavailable too.
Ransomware Reality
Backup is your last clean exit
Modern ransomware does more than lock files. It looks for backup systems, admin accounts, and recovery tools, then tries to erase your way out before you notice.
Paying is not a strategy. Paying funds the next attack, does not guarantee decryption, and does not undo leaked data. A clean, isolated, tested recovery path is.
What leadership should assume
If attackers get deep enough to encrypt production systems, they will also try your backups. Isolation and immutability are business controls, not technical extras.
The Critical Distinction
Backup is inventory. Recovery is the plan.
- 1
Backup exists
Jobs are scheduled. Storage is full of copies. Dashboards look green.
- 2
Nobody tried a restore
No one has recovered a full system under time pressure. Gaps stay invisible.
- 3
Incident hits
Leadership asks for a recovery time. The real answer is “we’ll know when we finish.”
- 4
Business pays twice
Once for the outage. Again for the scramble to invent a plan mid-crisis.
Two Numbers That Matter
How long offline. How much work lost.
you’re open again?
Hours matter differently by role. A half-day outage for finance may be recoverable. A half-day outage for a clinic, call center, or warehouse may not be.
Leadership question: Which systems must return in under 4 hours? Under 24?
work can you re-do?
Backups are snapshots in time. If the last good copy is from last night, today’s invoices, charts, and files may be gone, even if systems come back.
Leadership question: Is losing 1 hour of data acceptable? 4 hours? A full day?
What Good Looks Like
A recovery program executives can recognize
3-2-1 rule
Three copies of critical data, on two different kinds of storage, with one copy offsite, so one failure cannot take everything.
Isolated copies
At least one recovery path attackers cannot quietly encrypt or delete from a compromised admin account.
Tested restores
Regular, documented proof that files and systems can actually come back, not just that backup jobs finished.
Named owners
Who declares an incident, who authorizes failover, who talks to clients. Roles written down before the crisis.
Business priorities
Restore order matches revenue and risk: clients first, then core ops, then everything else.
Visible reporting
Leadership sees pass/fail restore tests and open gaps in plain language, not only technical green lights.
Executive Checklist
Five questions to ask this week
- 1
What are our top 5 systems that must return first?
If everything is “critical,” nothing is prioritized under pressure.
- 2
When did we last restore something that mattered?
Ask for a date, what was restored, and whether it met the target time.
- 3
Where does our last clean copy live if the building is gone?
One site only is a single point of failure, including cloud-only without isolation.
- 4
Can ransomware wipe our backups from the same login that runs IT?
If yes, isolation is incomplete. That is a business risk, not a technical footnote.
- 5
Who decides, who recovers, who communicates, by name?
Plans without people are documents. People without plans improvise.
Side by Side
The cost of waiting is paid later
- Decisions made under panic
- Unclear recovery order
- Unknown time to reopen
- Possible ransom pressure
- Client updates improvised
- Insurance & legal scramble
- Roles already assigned
- Systems restored by priority
- Known time targets
- Clean path that avoids paying
- Client message already drafted
- Evidence you took due care
BRITECITY
Questions?
The right next step is not more tools. It is clarity on how you come back.
Walk your top systems against those five leadership questions. Where answers are vague, that is the risk.
Your techTEAM can map recovery time, data loss tolerance, and restore proof, in business language.
Can you open tomorrow? That is the only score that counts.
Make IT Easy