[Company name]
IT Disaster Recovery Plan
| Organization | [Company name] |
|---|---|
| Document | IT Disaster Recovery Plan |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose and Scope
This IT Disaster Recovery Plan ("the Plan") describes how [Company name] will restore its critical technology systems and data after a disruptive event. Its goal is to limit downtime and data loss, protect client and employee information, and return the business to normal operations in a controlled, documented way.
The Plan covers all company-owned and company-managed technology used to run the business, including:
- Servers, network equipment, and internet connectivity at [Primary office address]
- Cloud services, including [Email / productivity platform] and [Main line-of-business application]
- Company laptops, desktops, and mobile devices
- Backup systems provided by [Backup solution / provider], including copies stored at [Offsite / cloud backup location]
- Phone systems, printers, and other connected equipment that the business depends on
This Plan addresses the technology recovery portion of business continuity. Decisions about staffing, customer communications, and physical facilities are covered in the Business Continuity Plan, and security incidents such as ransomware follow the Incident Response Plan first, then use this Plan to restore systems.
2. Disaster Scenarios Covered
The Plan is written to handle the events most likely to affect a small business in the Tampa Bay area:
| Scenario | Examples | Primary response |
|---|---|---|
| Hardware failure | Server, storage, firewall, or switch failure | Replace or fail over; restore from local backup |
| Cyberattack | Ransomware, destructive malware, compromised administrator account | Incident Response Plan first; then clean restore from isolated or immutable backup |
| Cloud service outage | Email, line-of-business, or identity provider outage | Follow provider status; use documented workarounds |
| Loss of site | Fire, flooding, hurricane damage, building closure | Work from alternate location; restore to cloud or replacement hardware |
| Extended power or internet loss | Utility outage after a storm, fiber cut | UPS and generator procedures; cellular backup; remote work |
| Human error | Accidental deletion, misconfiguration | Point-in-time restore from backup |
3. Roles and Responsibilities
| Role | Assigned to | Responsibilities |
|---|---|---|
| DR Coordinator | [DR coordinator name] | Declares a disaster, activates the Plan, coordinates the recovery team, approves spending, and communicates with leadership. |
| Backup DR Coordinator | [Backup DR coordinator] | Acts as DR Coordinator if the primary is unavailable. |
| Executive sponsor | [Approver name] | Approves major decisions (relocation, large purchases, public statements, insurance claims). |
| Technical recovery lead | [IT contact] ([IT provider / MSP]) | Assesses damage, restores systems in priority order, verifies data integrity, and documents actions. |
| Communications lead | [Owner name] | Keeps employees, clients, and vendors informed using approved messages. |
| Department contacts | One per team | Confirm their applications work after restore and report problems. |
Drafting note: In a small company one person often holds several roles. That is fine, but every role must have a named backup who can reach this Plan without access to the office or the company network.
4. Emergency Contact Tree
When a disaster is suspected, the person who discovers it contacts the DR Coordinator immediately. The DR Coordinator then activates the tree below. Each person calls the people assigned to them and reports back when everyone has been reached.
- Discoverer calls the DR Coordinator, [DR coordinator name], at [DR coordinator mobile]. If there is no answer within 15 minutes, call the Backup DR Coordinator, [Backup DR coordinator].
- The DR Coordinator calls the technical recovery lead, [IT contact], at [IT contact phone] or [IT contact email], and the executive sponsor, [Approver name].
- The communications lead notifies department contacts, who notify their team members.
- The DR Coordinator contacts outside parties as needed (see table below).
| Contact | Organization | Phone | When to call | |
|---|---|---|---|---|
| [DR coordinator name] | [Company name] | [DR coordinator mobile] | Any suspected disaster | |
| [IT contact] | [IT provider / MSP] | [IT contact phone] | [IT contact email] | All technology outages |
| Backup provider support | [Backup solution / provider] | Restore failures, lost backup access | ||
| Cyber insurance claims | [Cyber insurance carrier] | [Insurer claims / breach hotline] | Any cyberattack, before paying or engaging outside vendors | |
| Internet service provider | Connectivity outage | |||
| Electric utility | Power outage | |||
| Building / landlord | Facility damage or access | |||
| Legal counsel | [Legal counsel] | Data exposure, regulatory questions |
Drafting note: Print this contact list and store a copy off-site and in the company password manager or a shared cloud folder that does not depend on the office network. Include personal mobile numbers; office phones may be down.
5. Critical Systems and Recovery Objectives
The Recovery Time Objective (RTO) is the maximum acceptable time a system can be down. The Recovery Point Objective (RPO) is the maximum acceptable amount of data loss, measured in time. Systems are restored in priority order. The values below are starting points; adjust them based on what the business can actually tolerate and what your backup design can deliver.
| Priority | System / data | Business function | RTO | RPO | Recovery method |
|---|---|---|---|---|---|
| 1 | Internet, firewall, and core network | Access to everything else | 4 hours | n/a | Spare firewall or ISP replacement; cellular failover |
| 1 | Identity and email ([Email / productivity platform]) | Communication, sign-in to cloud apps | 4 hours | 1 hour | Cloud provider; restore mailboxes from third-party backup if needed |
| 1 | [Main line-of-business application] | Core operations and client service | 8 hours | 1 hour | Restore server image or vendor cloud recovery |
| 2 | File server / shared files | Documents and records | 24 hours | 4 hours | Restore from [Backup solution / provider] |
| 2 | Accounting system | Billing, payroll, payables | 24 hours | 24 hours | Restore from backup or vendor cloud |
| 3 | Phones / VoIP | Inbound calls | 24 hours | n/a | Forward numbers to mobiles via provider portal |
| 3 | Printers and scanners | Printing, scanning | 72 hours | n/a | Reinstall drivers; temporary devices |
| 3 | Individual workstations | Staff productivity | 72 hours | 24 hours | Reimage or replace; users work from cloud apps |
Drafting note: If an RTO is shorter than your backup design can achieve (for example, 4 hours to restore a large server from a cloud-only backup), either invest in faster recovery (local backup appliance, virtualization, standby hardware) or accept a longer RTO in writing. The mismatch is the most common flaw in small business DR plans.
6. Backup Summary
Detailed backup requirements are in the Data Backup Policy. In summary, [Company name] follows the 3-2-1 approach: at least three copies of important data, on two different types of storage, with at least one copy off-site and protected from deletion or encryption by an attacker.
| What is backed up | Frequency | Local copy | Off-site copy | Retention |
|---|---|---|---|---|
| Servers (full image) | Hourly incremental, nightly | Backup appliance / NAS | [Offsite / cloud backup location] | 30 daily, 12 monthly |
| [Email / productivity platform] mail, OneDrive/SharePoint or equivalent | At least daily | n/a (cloud) | Third-party cloud backup | 1 year minimum |
| [Main line-of-business application] database | Hourly or per vendor guidance | Backup appliance | [Offsite / cloud backup location] | 30 days minimum |
| Firewall and switch configurations | After every change | IT documentation system | Cloud copy | Last 5 versions |
Backup credentials and encryption keys are stored in [Company password manager] and are accessible to at least two authorized people. At least one backup copy must be unreachable with normal administrator credentials (immutable, air-gapped, or managed under separate accounts).
7. Disaster Declaration and Plan Activation
The DR Coordinator (or backup) declares a disaster when any of the following is true:
- A Priority 1 system is down, or is expected to be down, longer than its RTO
- The office is inaccessible or unsafe, or is expected to be for more than one business day
- Ransomware or destructive malware is confirmed on any company system
- Data loss exceeds the RPO for any Priority 1 or 2 system
On declaration, the DR Coordinator will:
- Confirm the safety of all staff before any recovery activity.
- Activate the contact tree and open an incident log (time, action, person) that is kept for the whole event.
- Engage [IT provider / MSP] and agree on an initial assessment window (target: within 2 hours).
- If a cyberattack is suspected, follow the Incident Response Plan and notify [Cyber insurance carrier] before restoring, wiping, or rebuilding systems, so that evidence and coverage are preserved.
- Choose a recovery strategy (repair in place, restore on-site, restore to cloud, or relocate) with the executive sponsor.
- Set an update schedule for staff and clients (for example, every 4 hours during business hours).
8. Recovery Procedures
Procedure A: Server or storage failure
- Confirm the failure and check whether the hardware is under warranty or support contract.
- If repair will exceed the RTO, start a restore of the most recent good backup to standby hardware, a virtual host, or the backup appliance's instant-recovery feature.
- Verify the restored server boots, services start, and data is current to within the RPO.
- Have each department contact test their applications and sign off.
- Once the original hardware is repaired, schedule a planned move back outside business hours.
Procedure B: Ransomware or destructive attack
- Follow the Incident Response Plan: isolate affected systems, preserve evidence, and notify the insurer and legal counsel.
- Do not restore until the technical lead confirms the attacker's access has been removed (passwords reset, malicious accounts removed, entry point closed).
- Identify the last clean backup point, taking into account that attackers may have been present days or weeks before encryption.
- Rebuild systems from known-good media or images, then restore data from the clean backup.
- Scan restored data, reset all credentials, and monitor closely for at least 30 days.
Procedure C: Cloud service outage
- Check the provider's status page and admin portal to confirm the outage is on the provider's side.
- Notify staff of the outage and the expected workaround (for example, use mobile apps, work offline, or delay non-urgent tasks).
- If the outage exceeds the RTO, consider restoring critical mailboxes or files from the third-party backup to an alternate location.
- Record the outage duration for vendor review.
Procedure D: Loss of the office
- Direct staff to work from home or from the alternate site: [Alternate work location].
- Forward the main phone number to mobile phones or a cloud phone system.
- Restore Priority 1 systems to cloud infrastructure or replacement hardware at the alternate site.
- Issue replacement laptops as needed, enrolled through [Device management (MDM) tool] and secured before use.
- Document damaged equipment with photos and serial numbers for insurance.
After recovery
- All Priority 1 and 2 systems confirmed working by department contacts
- Backups re-established and a successful new backup completed
- Temporary workarounds and forwarding rules removed
- Incident log closed and filed
- Lessons-learned meeting held within 10 business days and this Plan updated
9. Testing and Maintenance
A plan that has not been tested should be assumed not to work. [Company name] will test the Plan on the following schedule:
| Test | Frequency | Owner | Success criteria |
|---|---|---|---|
| Backup job review (success/failure alerts) | Daily or weekly | [IT provider / MSP] | All jobs successful or failures remediated within 1 business day |
| File and mailbox restore test | Monthly | [IT provider / MSP] | Sample files restored intact within 1 hour |
| Full server restore test | Quarterly | [IT provider / MSP] | Server restored and verified within its RTO |
| Tabletop exercise (walk through a scenario) | Annually | [DR coordinator name] | Team completes scenario; gaps recorded |
| Contact tree test | Twice a year (once before June 1) | [DR coordinator name] | All contacts reached within 1 hour |
| Plan review and update | [Review frequency] | [Owner name] | Plan reflects current systems, people, and vendors |
Test log
| Date | Test performed | Result | Issues found | Follow-up / owner |
|---|---|---|---|---|
The Plan must also be updated whenever a critical system is added or retired, a key person or vendor changes, or the office moves.
10. Annex A: Hurricane and Severe Weather Procedures
Atlantic hurricane season runs June 1 through November 30. Because [Company name] operates in Florida, these steps supplement the procedures above whenever a tropical storm or hurricane threatens the area. Staff safety always comes first: no one should stay at or return to the office against evacuation orders to protect equipment.
Before the season (complete by June 1)
- Review this Plan and update the contact tree with current personal mobile numbers
- Confirm backups are current and run a test restore from the off-site copy
- Verify every employee can work remotely: laptop, VPN or cloud access, MFA on their phone
- Test UPS batteries and replace any that fail; confirm generator service if applicable
- Confirm the office evacuation zone and the alternate work location ([Alternate work location])
- Photograph and inventory IT equipment (serial numbers, purchase dates) for insurance
- Review cyber and property insurance coverage for business interruption
Storm watch: about 72 hours out
- DR Coordinator confirms who is responsible for each step below
- Verify the latest off-site backup completed successfully
- Send staff a reminder to take laptops, chargers, and MFA devices home each night
- Confirm the phone forwarding procedure and test it
- Postpone non-essential IT changes and updates
Storm warning: about 48 hours out
- Run a final full backup and confirm it replicated off-site
- Move equipment off the floor and away from windows; cover with plastic sheeting
- Label and photograph network cabling if equipment will be disconnected
- Notify clients of possible service disruptions and alternate contact methods
Final 24 hours
- Gracefully shut down servers, storage, and network equipment in the documented order
- Unplug equipment from wall power to protect against surges when power returns
- Forward the main phone number to mobiles or the cloud phone system
- Post an out-of-office message and website notice if the office will close
- Confirm all staff check-in procedures (who checks in with whom, and how)
After the storm
- Confirm staff safety through the check-in procedure before discussing work.
- Do not enter the building until authorities and the landlord say it is safe.
- Inspect for water damage before applying power. Do not power on wet equipment.
- Power up in order: network and firewall, storage, servers, then workstations. Wait for stable utility power or run on generator with surge protection.
- Verify systems and data; if equipment is damaged, activate Procedure D (Loss of the office).
- Document damage with photos for insurance and keep receipts for emergency purchases.
- Hold a short debrief and update this annex with what worked and what did not.
11. Plan Distribution
Copies of this Plan are kept in the following locations so it is available even if company systems are down:
- Printed copy with the DR Coordinator and the Backup DR Coordinator (kept at home)
- Shared cloud folder accessible from any device
- Stored with [IT provider / MSP]
- Secure note in [Company password manager]
All employees are told where to find the Plan and who the DR Coordinator is during onboarding and during the annual review.
12. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this IT Disaster Recovery Plan | [Owner name] |
13. Approval
This IT Disaster Recovery Plan has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free IT Disaster Recovery Plan template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
