Skip to main content
Altivus

Cybersecurity and Digital Resilience

You have backups. Could your business actually recover?

Most businesses can tell you their backups ran last night. Fewer can say how long it would take to get orders moving again if the main server failed this morning. This guide is the list of questions that closes that gap.

What a “backup succeeded” email tells you

It tells you a copy job finished. It doesn’t tell you whether your team could get back to work after an outage, or how long that would take.

Getting back to work usually needs more than the files. People need the application, their access, a working connection and any other service the process relies on, often in a particular order. A recovery plan should make that order clear to the people who run the business.

CISA recommends protecting backup copies and testing restores. The useful question for a business leader is simple: what have we actually tested, and what did we learn?

Decide what has to come back first

Start with the business activity: taking orders, serving customers, getting to essential records. Then work out which systems and people that activity depends on.

Two questions help here: how long can the business cope without it, and how much recent work could you afford to lose? IT people call the answers recovery time and recovery point objectives. They’re targets you agree, test and, where it applies, put in a contract.

It also helps to agree who can authorize recovery work, and what would show that people can genuinely work again, beyond a system simply switching on.

Questions to ask whoever runs your backups

Ask the people who do the work what a successful recovery would look like to them. Their answer helps the technical team design a test that means something. Any restore test should say what it covered and what it didn’t.

  • What’s protected, and what isn’t?
  • Who can get to the backup copies, and how is that controlled?
  • What was last restored in a test, and when?
  • Did the test include everything people need to actually work?
  • Who checked the restored data?
  • What failed, or took longer than expected?
  • Who owns the open actions, and when is the next review?

If nobody knows the answer

Not knowing the last test date is a reason to ask for the record. It doesn’t mean you’ve been breached or that every backup is useless. And one good test doesn’t mean every future outage will go smoothly.

Use the checklist to guide a conversation with whoever runs your backups. Don’t try a restore or change backup settings just to fill it in; a real test needs permission, a plan and safeguards.

Recovery-readiness questions for business leaders

Write down what you know, what you’d like to see and who owns each item. It’s a conversation aid, so leave the restore itself to the people responsible.

QuestionKnown answer or evidenceOwnerNext step
Which business activity returns first?
What is protected and excluded?
Who authorizes and performs recovery?
When was restoration last tested?
Were dependencies and output checked?
What did the test not prove?
Which actions remain unresolved?
Recovery-readiness questions for business leaders

Keep your completed notes within your own team.

Sources

Talk to us

Want a second opinion on your recovery plan?

Tell us which parts of the business can’t go down and how backups work today. Keep passwords and system details out of the form.

Office address
151 FM-407
Suite 200
Argyle, TX 76226

Fields marked are required.

What can we help with?

A short business explanation is enough. Please don’t include passwords or confidential records.

We use these details to respond to you. See our Privacy Policy.