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
[Assess the incident and its likely duration (within 30 minutes of detection).]
[Declare a disaster and record the time; this starts the RTO clock.]
[Call the DR team to the bridge line [number / link]; if Microsoft 365 is down, use the fallback group text list.]
[Notify the business liaison, who informs the Management Board.]
[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
[Confirm secondary site connectivity and firewall are up; apply the latest backed-up firewall configuration if needed.]
[Verify the replica domain controller is healthy; seize roles if the primary is lost.]
[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.]
[Update DNS records to point services to the secondary site (procedure DR-NET-04).]
[Confirm staff can authenticate to remote access with MFA.]
8.2 Tier 1: Document management system
[Confirm the latest clean snapshot (in a cyber incident, choose a snapshot from before the earliest sign of compromise, agreed with the security lead).]
[Promote the replicated volume at the secondary site.]
[Start database and application servers in order: database, index, application, web.]
[Run the integrity check script and open ten test matters to verify documents.]
[Re-point the practice-management integration and notify users.]
8.3 Tier 2: Finance and billing system
[Restore the finance VM and database from the most recent clean backup at the secondary site.]
[Apply transaction logs to reach the recovery point.]
[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
[Confirm the primary site or rebuilt environment is secure and stable.]
[Plan the fail-back during a low-impact window and get business sign-off.]
[Synchronise data from the secondary site back to primary and verify.]
[Switch services back and monitor for 48 hours.]
[Stand down the DR team and record the end time.]
[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] |