Skip to content
GraviPointThe Centre of Productivity
  • AI AgentNew
  • Pricing
  • Community
Log inGet started free
TemplatesCorporate & AdministrationIT & Asset ManagementIT Disaster Recovery Plan

DocumentIT & Asset ManagementFree

IT Disaster Recovery Plan

Recover critical systems on time: RTO and RPO per system, activation, recovery procedures, contacts and test schedule.

Shown with sample data

Colour

IT Disaster Recovery Plan

Organisation

[Greystone & Hale LLP]

Plan owner

[Name, IT Director]

Approved by

[Name, Managing Partner]

Version and date

[4.0, November 2026]

Last tested

[Partial failover, 18 September 2026]

Next review

[May 2027]

Copies held

[IT SharePoint (DR folder), printed copy in IT Director’s and Office Manager’s grab bags, offline encrypted USB]

1. Purpose and scope

[This plan describes how Greystone & Hale will recover its critical IT systems and data after a disaster affecting its London office server room, its cloud services or its network. It covers systems listed in section 5. Wider business continuity (premises, people, client communications) is covered in the Business Continuity Plan.]

2. Assumptions

  • [Staff can work remotely on company laptops if the office is unavailable.]

  • [Cloud services (Microsoft 365, the practice-management system) are recovered by their providers under contract; we recover our configuration and data.]

  • [The secondary site is the colocation facility in [location], 40 miles from the office.]

  • [At least two members of the DR team are available.]

3. Disaster scenarios covered

Scenario

Example

[Cyber attack]

[Ransomware encrypts servers and on-site backups]

[Site loss]

[Fire, flood or power failure in the office server room]

[Cloud or supplier outage]

[Major outage at the cloud provider or internet provider]

[Hardware failure]

[Storage array failure]

[Human error]

[Accidental deletion of a document management repository]

4. DR team and contacts

Role

Name

Responsibilities

Mobile

Deputy

DR coordinator

[IT Director]

[Declares disaster, leads recovery, reports to management]

[Phone]

[Infrastructure Manager]

Infrastructure lead

[Infrastructure Manager]

[Network, identity, servers, storage, backups]

[Phone]

[Senior Engineer]

Applications lead

[Applications Manager]

[Document management, practice management, finance system]

[Phone]

[Applications Analyst]

Security lead

[Security Officer]

[Forensics, containment, safe restoration in cyber incidents]

[Phone]

[MSSP duty manager]

Business liaison

[Chief Operating Officer]

[Priorities, staff and client communications]

[Phone]

[Office Manager]

Supplier contacts

Supplier

Service

Support line

Contract or reference

[Colocation provider]

[Secondary site]

[24/7 phone]

[Contract no.]

[Backup vendor]

[Backup software and immutable cloud copy]

[24/7 phone]

[Customer ID]

[Managed security provider]

[Monitoring and incident response]

[24/7 phone]

[Contract no.]

[Internet provider]

[Primary and backup circuits]

[24/7 phone]

[Circuit IDs]

[Cyber insurer]

[Incident hotline]

[24/7 phone]

[Policy no.]

5. System inventory, RTO and RPO

Tier

System

Business owner

RTO

RPO

Recovery method

0

[Identity (Active Directory, Entra ID), DNS, firewalls]

[IT Director]

[4 hours]

[24 hours]

[Replica domain controller at secondary site; firewall configs backed up]

1

[Document management system]

[Head of Knowledge]

[8 hours]

[1 hour]

[Storage replication to secondary site; hourly snapshots]

1

[Practice management and time recording]

[COO]

[8 hours]

[Provider-managed (15 min)]

[SaaS: provider DR; we restore integrations]

1

[Email and Microsoft 365]

[IT Director]

[4 hours]

[Provider-managed]

[SaaS; third-party backup for deletion and ransomware]

2

[Finance and billing system]

[Finance Director]

[24 hours]

[4 hours]

[Restore VM from backup at secondary site]

2

[Remote access gateway]

[IT Director]

[8 hours]

[24 hours]

[Standby gateway at secondary site]

3

[Intranet and HR system]

[Head of People]

[72 hours]

[24 hours]

[Restore from backup]

3

[Print services]

[Office Manager]

[5 days]

[n/a]

[Rebuild]

Gap: the finance system currently restores in about 30 hours in tests against a 24-hour RTO. Action: move to replicated storage by March 2027 (owner: Infrastructure Manager).

6. Backup strategy

Data

Frequency

Retention

Copies

[Servers (VMs)]

[Nightly, plus hourly snapshots for document management]

[35 daily, 12 monthly]

[On-site appliance, secondary site replica, immutable cloud copy]

[Microsoft 365]

[3 times daily]

[7 years]

[Third-party cloud backup]

[Network device configurations]

[On change and weekly]

[1 year]

[Backup server and offline copy]

7. Activation

7.1 Who can declare a disaster

[The DR coordinator or their deputy, after consulting the business liaison where possible. In a cyber incident, the security lead must confirm it is safe to begin restoration.]

7.2 Activation criteria

  • [Any Tier 0 or Tier 1 system is unavailable, or is expected to be unavailable for longer than half its RTO.]

  • [Loss of the office server room.]

  • [Confirmed ransomware or destructive attack.]

7.3 Activation steps

  1. [Assess the incident and its likely duration (within 30 minutes of detection).]

  2. [Declare a disaster and record the time; this starts the RTO clock.]

  3. [Call the DR team to the bridge line [number / link]; if Microsoft 365 is down, use the fallback group text list.]

  4. [Notify the business liaison, who informs the Management Board.]

  5. [In a cyber incident, call the insurer’s hotline and the managed security provider before restoring anything.]

8. Recovery procedures

8.1 Tier 0: Identity, network and DNS

  1. [Confirm secondary site connectivity and firewall are up; apply the latest backed-up firewall configuration if needed.]

  2. [Verify the replica domain controller is healthy; seize roles if the primary is lost.]

  3. [In a cyber incident, reset the KRBTGT account twice, reset all privileged passwords and use break-glass accounts held in the sealed envelope in the safe.]

  4. [Update DNS records to point services to the secondary site (procedure DR-NET-04).]

  5. [Confirm staff can authenticate to remote access with MFA.]

8.2 Tier 1: Document management system

  1. [Confirm the latest clean snapshot (in a cyber incident, choose a snapshot from before the earliest sign of compromise, agreed with the security lead).]

  2. [Promote the replicated volume at the secondary site.]

  3. [Start database and application servers in order: database, index, application, web.]

  4. [Run the integrity check script and open ten test matters to verify documents.]

  5. [Re-point the practice-management integration and notify users.]

8.3 Tier 2: Finance and billing system

  1. [Restore the finance VM and database from the most recent clean backup at the secondary site.]

  2. [Apply transaction logs to reach the recovery point.]

  3. [Finance team verifies the last posted invoices and bank reconciliation before use.]

Detailed runbooks with screenshots, server names and commands are held in the DR folder: [location].

9. Communications

Audience

Message

Channel

Owner

When

[Management Board]

[Situation, impact, expected recovery times]

[Phone, then email]

[Business liaison]

[Within 1 hour of declaration, then every 4 hours]

[All staff]

[What is affected, how to work, next update time]

[Text message, personal email if M365 down]

[Business liaison]

[Within 2 hours, then twice daily]

[Clients]

[Service impact and alternative contact methods]

[Partners by phone; website notice]

[COO]

[As agreed with Management Board]

[Regulators, insurer]

[Notification if required]

[Per breach plan]

[Compliance Officer]

[Per legal deadlines]

10. Return to normal operations

  1. [Confirm the primary site or rebuilt environment is secure and stable.]

  2. [Plan the fail-back during a low-impact window and get business sign-off.]

  3. [Synchronise data from the secondary site back to primary and verify.]

  4. [Switch services back and monitor for 48 hours.]

  5. [Stand down the DR team and record the end time.]

  6. [Hold a post-incident review within 10 working days and update this plan.]

11. Test schedule

Test

Scope

Frequency

Next date

Owner

[Backup restore test]

[Restore 5 random files and one VM; check integrity]

[Monthly]

[Monthly, first Tuesday]

[Senior Engineer]

[Immutable copy restore]

[Restore a VM from the immutable cloud copy]

[Quarterly]

[February 2027]

[Infrastructure Manager]

[Tabletop exercise]

[Ransomware scenario with DR team and Management Board]

[Annually]

[March 2027]

[IT Director]

[Partial failover]

[Tier 0 and Tier 1 systems to secondary site out of hours]

[Annually]

[September 2027]

[IT Director]

[Contact list check]

[Call every number in section 4]

[Quarterly]

[January 2027]

[Office Manager]

Last test results

System

RTO target

Achieved

RPO target

Achieved

Pass?

[Identity and DNS]

[4 h]

[2 h 40 min]

[24 h]

[12 h]

[Yes]

[Document management]

[8 h]

[5 h 15 min]

[1 h]

[45 min]

[Yes]

[Finance system]

[24 h]

[30 h]

[4 h]

[3 h]

[No: see gap in section 5]

12. Plan maintenance

[The plan owner reviews this plan every six months, after each test, after any significant change to systems or suppliers, and after any real activation. Changes are recorded below.]

Version

Date

Change

Author

[4.0]

[Nov 2026]

[Added immutable backup restore; updated contacts]

[IT Director]

[3.2]

[Mar 2026]

[Moved email backup to new vendor]

[Infrastructure Manager]

Text in [brackets] is yours to replace.

  • About
  • What’s included
  • How to use
  • Questions
  • Related resources

About this template

A disaster recovery plan is the IT runbook for getting critical systems back after a ransomware attack, data-centre failure or cloud outage. This plan sets recovery time and recovery point objectives for every system by tier, the backup and recovery strategy, who declares a disaster and how, the DR team and contacts, step-by-step recovery procedures, communications, return to normal operations and an annual test schedule, worked through for a fictional law firm.

Who it’s for

  • Cyber insurance and client security audits
  • Ransomware preparedness
  • Organisations with on-premises and cloud systems
  • Supporting a wider business continuity plan

What’s included

  • 1. Purpose and scope
  • 2. Assumptions
  • 3. Disaster scenarios covered
  • 4. DR team and contacts
  • 5. System inventory, RTO and RPO
  • 6. Backup strategy
  • 7. Activation
  • 8. Recovery procedures
  • 9. Communications
  • 10. Return to normal operations

How to use it

  1. 1Agree RTO and RPO for each system with business owners; they decide how much downtime and data loss is acceptable.
  2. 2Check your backups and infrastructure can actually meet those objectives, and record any gaps with a plan to close them.
  3. 3Write recovery procedures detailed enough that a competent engineer who did not build the system could follow them.
  4. 4Store the plan, contacts and credentials-access instructions where they are available when systems are down.
  5. 5Test at least annually, record the actual recovery times against targets and fix what fails.

Tips

  • Assume your primary environment and normal admin accounts are unavailable or compromised: keep break-glass accounts and an offline copy of this plan.
  • Protect at least one backup copy from ransomware by making it immutable or offline, and restore from it in tests.
  • Recover in dependency order. Identity, networking and DNS usually come before the applications that depend on them.

Questions

What is the difference between RTO and RPO?

Recovery time objective (RTO) is the maximum acceptable time to restore a system after a disruption. Recovery point objective (RPO) is the maximum acceptable data loss, measured as time since the last good backup or replica.

What is the difference between disaster recovery and business continuity?

Business continuity covers how the whole organisation keeps operating (people, premises, suppliers, processes). Disaster recovery is the IT part: restoring systems and data.

How often should a disaster recovery plan be tested?

At least once a year for a full or partial failover test, with backup restore tests more often (monthly or quarterly) and a tabletop walkthrough when the plan changes.

Related searchesit disaster recovery plan templatedisaster recovery plandrp templaterto rpo tableit recovery planbackup and recovery plan

Details

Format
Document
Category
IT & Asset Management
Setup
150 min
Level
Advanced
Price
Free

Download a copy

Downloads need a free account.

DocumentIT & Asset ManagementFree

IT Disaster Recovery Plan

Recover critical systems on time: RTO and RPO per system, activation, recovery procedures, contacts and test schedule.

A free account keeps your copy safe so you can come back to it. Have one? Log in

Download a copy

Downloads need a free account.

Details

Format
Document
Category
IT & Asset Management
Setup
150 min
Level
Advanced
Price
Free

Your copy is private to you.

More it & asset management templates

View all
IT Asset Inventory3 sheets

Devices in use

9

Due for refresh

4

Out of warranty

8

ABCD
1Asset tagTypeMake and modelSerial number
2IT-001LaptopMacBook Pro 14"C02FX1Z2MD6R
3IT-002LaptopDell Latitude 74407HX92K3
4IT-003MonitorLG 27" 4K405NTPC1A882
5IT-004PhoneiPhone 15F2LXK9P1N7
Assets
SpreadsheetIT & Asset Management

IT Asset Inventory

Every laptop, phone and device with assignee, serial, warranty, age, refresh date and depreciated value, plus counts and spend by type.

10 min setupPreview
Software License Tracker2 sheets

Annual software spend

$20,407

Seat utilisation

80%

Wasted per year

$5,456

ABCD
1SoftwareCategoryOwnerPlan
2Google WorkspaceProductivityITBusiness Standard
3SlackProductivityITPro
4FigmaDesignDesign leadProfessional
5GitHubEngineeringEng leadTeam
Licenses
SpreadsheetIT & Asset Management

Software License Tracker

Every subscription with seats bought and used, utilisation, annual cost, wasted spend, renewal and notice dates, plus spend by category.

10 min setupPreview
IT Help Desk Ticket Log2 sheets

Open tickets

4

Average days to resolve

2

Resolved within target

75%

ABCD
1TicketOpenedRequesterIssue
2T-1041Nov 2Lena ParkLaptop will not charge
3T-1042Nov 2Jordan LeeCannot log in to CRM after password reset
4T-1043Nov 3Grace LimAccounting software licence expired
5T-1044Nov 4Tom ReyesWi-Fi drops in meeting room 2
Tickets
SpreadsheetIT & Asset Management

IT Help Desk Ticket Log

Log support requests with priority and owner, and measure resolution time against your service targets.

10 min setupPreview

Practical guides and new resources, monthly.

One short email with new templates, calculators and how-tos. Unsubscribe any time.

GraviPointThe Centre of Productivity

Find the right resource. Make it work for you. Get things done with spreadsheets, documents, forms and calculators you can use right in your browser.

support@gravipoint.com
  • @gravipoint
  • @GraviPoint
  • GraviPoint
  • 𝕏@gravipoint

Templates

  • All templates
  • Budgets & expenses
  • Invoices & billing
  • Project management
  • HR & people
  • Inventory & stock
  • Sales & CRM
  • Financial calculators

Popular

  • Monthly budget
  • Invoice
  • Employee shift schedule
  • Weekly timesheet
  • Project plan & Gantt chart
  • Inventory tracker
  • Expense report
  • Mortgage calculator

Solutions

  • Individuals & households
  • Freelancers & consultants
  • Founders & startups
  • Small business owners
  • Teams & operations
  • Students & educators

Company

  • About
  • Features
  • Pricing
  • Community
  • Journal
  • Contact
© 2026 GraviPoint. All rights reserved.
  • Privacy
  • Terms
  • Help centre
  • FAQ