IT disaster recovery plan: Why your IT partner shouldn’t go silent
Chad Odom, our owner, worked on site with our technicians through Hurricane Katrina, the 2016 floods and Hurricane Ida. Each one taught the same lesson: how fast you recover depends on the IT disaster recovery plan you made months earlier, and on whether your IT partner answers the phone when things go wrong.
The same is true of a ransomware note on the front desk computer at 4 p.m. on a Friday. A storm gives you a few days of warning. An attack gives you none.
Talk to an advisor
Ask about your own setup.
We ask what you’re trying to accomplish and tell you what we’d look at first. It costs nothing to talk, and no price comes up on this call.
What IT disaster recovery has to cover
A backup is a copy of your data. Disaster recovery is the work of getting systems and data back in a set order and within a set time. Business continuity is the larger plan for keeping the organization running while that happens. You can have a perfect backup and still be down for a week if nobody knows how long a restore takes, where replacement hardware will come from or how staff will work in the meantime.
Three kinds of events take offices offline:
- Severe weather and power loss. When Hurricane Ida made landfall in Louisiana in 2021, about half a million Louisiana customers were still without power more than a week later, according to the U.S. Energy Information Administration (EIA). In 2024, EIA found U.S. customers averaged 11 hours without power, nearly double the prior decade’s average, mostly because of hurricanes.
- Cyberattacks, which usually arrive with no warning. Verizon notes that small businesses are hit disproportionately.
- Everyday failures: a server or firewall dies, an update goes wrong, someone deletes the wrong folder, or a cloud vendor has an outage.
48%
of breaches in Verizon’s 2026 Data Breach Investigations Report involved ransomware
The ransomware scenario is the one plans most often miss, because ransomware can also encrypt or delete backups that are reachable from the network.
Before, during and after: what your IT partner should do
Most organizations find out how their IT provider handles a crisis only once the crisis has started.

| Stage | What a good IT partner does |
|---|---|
| Months before | Writes down recovery targets for each key system, tests restores, and keeps at least one backup copy that attackers can’t change or delete |
| When a storm is named | Sends a notice and a checklist, verifies backups and the off-site copy, runs controlled shutdowns and UPS checks, and confirms remote work and cloud failover are ready |
| During the event | Answers, isolates infected devices, and sends updates on a schedule everyone knows in advance |
| Afterward | Restores systems in priority order, then gives you a written account of what happened and what will change |
The second row is our own pre-storm routine for every client. Our hurricane disaster recovery checklist covers what your office should do on the same timeline.
For the events with no warning, every client has a 24/7 security operations center watching for attacks, we monitor client UPS units remotely, and our server backups run hourly, are copied off-site daily to storage in the US, are immutable and are verified by screenshot. Our business continuity services page tells the story of the Katrina server recovery.
Recovery can last much longer than the storm
The power comes back, the roads reopen, and the IT work keeps going. After Ida, we supported a nonprofit’s disaster case management program for 18 months, covering devices, systems, onboarding new staff, reporting and HR support.
Plan for that stretch as well as the first 72 hours. The weeks after a disaster often bring new hires, temporary locations, borrowed equipment and new reporting duties, all while your team is tired and distracted.
What a written disaster recovery plan should include
- A recovery time objective (RTO) for each key system. NIST defines RTO as how long a system can be in recovery before it seriously hurts the business. Phones and practice management software may need hours, while an archive server may be fine for a week.
- A recovery point objective (RPO), the point in time you need to recover to. It decides how often backups run.
- Backups in more than one place, with encrypted local copies for fast restores, cloud copies kept off site, and at least one copy attackers can’t modify or delete.
- A separate backup of Microsoft 365 email, OneDrive and SharePoint. Recycle bins and retention settings are a different thing.
- Tested restores: individual files often, and a full system at least once a year.
- A communication plan with contact lists that don’t depend on company email.
- A cyber incident playbook covering who to call first, how to isolate systems, and when to contact your insurer and counsel.
If you keep client, patient or financial records, parts of this are required. HIPAA’s contingency plan standard requires a data backup plan, a disaster recovery plan and an emergency mode operation plan, with periodic testing addressable. The FTC Safeguards Rule requires tax, accounting and other covered financial firms to keep a written incident response plan. Our compliance services keep those documents current, and our guide to the essentials of a business continuity plan covers the non-IT side.
Then test it. A tabletop exercise, where you walk through a scenario around a conference table, takes an hour or two and almost always turns up a gap, such as documentation that lives on the server that just went down.
Questions to ask your IT partner now
- How do we reach you in an emergency, including nights and weekends, and who answers?
- What are our recovery time and recovery point targets, and where are they written down?
- When did you last test a full restore of our systems, and how long did it take?
- Can ransomware on our network reach or delete our backups?
- Are our Microsoft 365 email and files backed up separately?
- How often will you update us during an incident, and will we get a written report afterward?
Specific answers are a good sign. Vague ones, or “we’ll handle it,” show you where the gaps are.
Find out how your provider would answer those six questions before hurricane season or a Friday afternoon forces the issue. To hear our answers and talk through your managed IT setup, book a 15-minute call.
For a real example, read how a two-site medical clinic came through Hurricane Ida in our business continuity case study.
Frequently asked questions
What should an IT disaster recovery plan include?
An IT disaster recovery plan should set a recovery time objective and a recovery point objective for each key system, keep backups in more than one place with at least one copy attackers can’t change, and back up Microsoft 365 separately. Add a communication plan that doesn’t depend on company email, a cyber incident playbook and a schedule for testing restores.
What is RTO and RPO?
RTO and RPO are the two targets that shape a recovery plan. The recovery time objective (RTO) is how long a system can be down before it seriously hurts the business. The recovery point objective (RPO) is the point in time you need to recover data to, and it decides how often backups have to run.
How often should you test a disaster recovery plan?
Test restores of individual files often and a full system at least once a year, and walk the team through the plan at least yearly. Test again whenever you add a key system, an office or a vendor. A tabletop exercise takes an hour or two and almost always turns up a gap.
What is a tabletop exercise in disaster recovery?
A tabletop exercise is a walkthrough of a disaster scenario around a conference table, such as ransomware on a Friday afternoon or a hurricane that closes the office. The team talks through who does what, in what order, and where the plan breaks. It often finds gaps like recovery documentation stored on the server that just went down.
Sources
- U.S. Energy Information Administration: Hurricane Ida caused at least 1.2 million electricity customers to lose power, 2021
- U.S. Energy Information Administration: Hurricanes in 2024 led to the most hours without power in 10 years, 2025
- Verizon: 2026 DBIR Executive Summary
- NIST glossary: Recovery Time Objective
- NIST glossary: Recovery Point Objective
- eCFR: 45 CFR 164.308, HIPAA administrative safeguards
- eCFR: 16 CFR 314.4, FTC Safeguards Rule elements
Next step
Let us handle this for you.
Hourly server backups copied off-site daily, and a written plan for storms and ransomware.
- 15 minutes
Tell us which question brought you here and how your office runs.
We’ll tell you how it applies to you and what we’d look at first.
If we’re not the right fit, we’ll say so.
