How to test backups before you need them

By David Freeland3 min read ·

The same line on every bill

It’s the last day of the month, and you’re signing off on the clinic’s bills. One line is the same one you see every month on the bill from your IT company: the backup service. It’s been on the bill for years, and you haven’t given it a second thought in a long time.

Today you do. Has anyone at the clinic ever gotten a file back from it? The backups are supposed to run every night. But no one has ever asked it for a file, so no one knows if one would come back.

Paying for a backup isn’t the same as knowing it works.

An untested backup is a guess

A smoke detector has a test button for a reason. You press it so you don’t find out the battery is dead during a fire. Backups work the same way. The test is a restore: you ask for a file back and check that it opens and looks right.

Until someone does that, a backup can fail without anyone noticing. Ransomware is one reason. The Cybersecurity and Infrastructure Security Agency (CISA) warns that many kinds of ransomware hunt for backups they can reach, then delete or lock them. That’s why CISA says to keep backups offline and to “regularly test the availability and integrity of backups.”

It happens to practices like yours. In 2025, a small physical therapy clinic in Michigan was hit by a cyberattack. According to HIPAA Journal’s report on the practice’s notice, the practice had to restore its data from backups. The restore failed, and it lost all of its patient information. It notified 4,764 current and former patients.

Think about what your clinic keeps on its own computers: x-rays, scanned intake forms, and signed consent forms. If your EHR software runs on the clinic’s own server, your patient charts are there too. If a restore fails, that information may be gone for good, along with years of your patients’ history.

Backups are part of your HIPAA plan

HIPAA’s Security Rule puts backups inside a clinic’s contingency plan, its plan for an emergency:

  • 45 CFR § 164.308(a)(7)(ii)(A) is the data backup plan. It requires procedures to keep “retrievable exact copies” of electronic patient information.
  • 45 CFR § 164.308(a)(7)(ii)(B) is the disaster recovery plan. It requires procedures “to restore any loss of data.”
  • 45 CFR § 164.308(a)(7)(ii)(D) adds “periodic testing and revision” of the contingency plan.

HHS guidance on ransomware is more direct. It says to run test restorations from time to time, to confirm that backed-up data is intact and that you can get it back.

A higher bar may be coming. A change HHS proposed in December 2024 would require written plans to bring certain systems and data back within 72 hours. It’s still a proposal. The federal regulatory agenda lists July 2027 as the target for a final rule.

Put your backups to the test

  • Restore one file: Pick a file your clinic uses, like an intake form or the fee schedule. Restore it to a different folder so the current copy stays put. Then open it and check that it’s whole and up to date.
  • Have your IT company show you: Ask when it last tested a restore, what it restored, and how long it took. Ask which computers are covered, including the x-ray computer, and which aren’t.
  • Keep one copy out of reach: Keep at least one backup offline or away from your network, where ransomware is less likely to find it. The FBI’s 2025 crime report recommends keeping backups off-site or offline.
  • Put it on the calendar: Repeat the test on a schedule, such as once a quarter. Test again after any big change, like replacing a computer or switching EHRs.

A restore test turns a guess into an answer. Restore one file this month, and the next time that line shows up on the bill, you’ll know what you’re paying for.

Disclaimer: This guide shares general information about HIPAA. It isn’t legal advice. For advice about your clinic, talk with a compliance professional or a lawyer who knows healthcare law.

Last reviewed November 12, 2026.

References & statutory citations

  1. Cybersecurity and Infrastructure Security Agency (CISA) and partners: #StopRansomware Guide (September 2023; opened November 12, 2026). (opens in a new tab)
  2. HIPAA Journal (a secondhand report of the practice’s notice; the practice’s own notice could not be found online on November 12, 2026): Small Michigan Physical Therapy Practice Reports Loss of Patient Data Due to Cyberattack (Steve Alder, July 23, 2025). (opens in a new tab)
  3. U.S. Department of Health and Human Services (HHS): 45 CFR § 164.308, Administrative safeguards (Code of Federal Regulations, revised as of October 1, 2025). (opens in a new tab)
  4. U.S. Department of Health and Human Services (HHS), Office for Civil Rights: Fact Sheet: Ransomware and HIPAA (July 11, 2016; opened November 12, 2026). (opens in a new tab)
  5. U.S. Department of Health and Human Services (HHS), Office for Civil Rights: HIPAA Security Rule Notice of Proposed Rulemaking to Strengthen Cybersecurity for Electronic Protected Health Information (fact sheet; content last reviewed December 27, 2024). (opens in a new tab)
  6. Office of Information and Regulatory Affairs (OIRA), Unified Agenda: HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (RIN 0945-AA22; Long-Term Actions; final action July 2027; opened November 12, 2026). (opens in a new tab)
  7. Federal Bureau of Investigation (FBI), Internet Crime Complaint Center (IC3): 2025 Internet Crime Report (page 15, “Recommendations to Protect Against Ransomware”; released April 2026). (opens in a new tab)