Skip to main content
Live webinar · Nov 3Register free →
Skip to main content

Guides/Template

A disaster recovery plan, written down and owned.

A plan nobody can find, or that names people who've left, won't help on the day. Use this template to write down what your recovery depends on, who owns each part, and how you'll prove it works. The PDF has blank tables to print and fill in.

A supercell thunderstorm with lightning striking the plains around a lone data center at dusk

What the plan covers

Everything a recovery depends on.

Start with the systems the business can't run without, then work outward.
  1. 01

    Recovery objectives

    RTO and RPO for each workload, backed by SLAs for backup frequency and retention.

  2. 02

    Copies and locations

    A primary copy and a secondary DR location, with immutable and air-gapped copies a cyberattack can't reach.

  3. 03

    Recovery plan for the backup platform

    How the data management infrastructure itself comes back first, because nothing else restores without it.

  4. 04

    Restore testing strategy

    How often restores are tested, which systems, and what a passing test looks like, for disaster and cyber scenarios.

  5. 05

    Clean recovery after an attack

    Recovery into an isolated cleanroom: isolate, check backups for threats, rebuild from a clean image, validate.

  6. 06

    Incident response plan

    Kept in step with the recovery plan, in support of NIST SP 800-61 and the Cybersecurity Framework.

1 · Recovery objectives

How fast, and how much data you can lose.

One row per workload. RTO is how long it can be down; RPO is how much recent data you can afford to lose.
WorkloadOwnerRTORPOBackup frequencyRetention
Student information systemName, role4 h15 minEvery 15 min7 years

2 · Copies and locations

Where every copy lives.

Every copy, where it is, what it's stored on, and whether an attacker could change it.
CopyLocationStorage typeImmutable or air-gapped?
Primary backupMain data centerDiskNo

3 · Recovery order

What comes back first.

Start with the backup platform and what it depends on; nothing else restores without it.
OrderSystemDepends onWho restores it
1Backup platformNetwork, storageKELYN / IT

4 · Testing

How you'll prove the plan works.

Which tests you run, on which systems, how often, and what happened last time.
TestSystemsHow oftenLast runResult
Restore testFile serversQuarterly

5 · Contacts

Who to call, written down.

Names and numbers on paper, with a backup for each role, because email and chat may be down too.
RoleNamePhoneBackup contact
Recovery lead

KELYN keeps your plan current, as a managed service.

KELYN plans, tests and keeps disaster recovery plans current, with a biannual KELYN Score review. Start with the free Cyber Readiness Scorecard, or talk to an engineer.