Backups That Actually Save a Practice

3-2-1 in plain English

The 3-2-1 rule is the oldest advice in backup, and it still works: keep 3 copies of your important data, on 2 different kinds of storage, with 1 copy somewhere completely separate — offsite or offline, where nothing on your network can reach it.

Why three copies? Because any single copy can fail, and failures travel in pairs: the server dies the same week the external drive does, or ransomware encrypts the live data and the backup sitting next to it. The offsite copy is the one that saves you when everything local is gone — fire, flood, theft, or encryption.

For a clinic, “important data” means the EHR database, imaging files, the practice management system, and the shared drive with HR and financial records. If losing it would stop you seeing patients or getting paid, it belongs in the 3-2-1 plan.

Why the backup you have probably won’t save you

Most practices we meet have something called a backup. Here is why it usually fails when it matters:

• It’s on the same network. Ransomware hunts for backups and encrypts them first. A USB drive plugged into the server is not a backup; it’s a second victim.
• Nobody ever tested a restore. Backups fail silently — corrupted files, jobs that stopped running months ago, credentials that expired. The only backup you can trust is one you’ve restored from.
• It doesn’t cover everything. The EHR is backed up, but the scanned insurance cards on the front-desk computer aren’t. The billing exports on a laptop aren’t. Partial backups produce partial recoveries.
• Nobody knows how long recovery takes. “We have backups” is not a plan. A plan says: we can be seeing patients again in four hours, because we proved it in March.

What a real backup setup looks like for a small clinic

Concretely, for a 10-to-25-person practice, a working setup looks like this. Your EHR and practice management data back up automatically every night to an encrypted device on-site — a network storage box, not a USB stick in the server. A second copy goes to secure cloud storage every night, out of reach of anything on your network. And on a regular schedule — weekly or monthly — a copy goes somewhere fully offline, like an encrypted drive that gets disconnected and stored offsite.

The key word in that paragraph is “automatically.” Backups that depend on someone remembering are backups that stop happening the week the office gets busy. Every job should run on a schedule, report success or failure to someone accountable, and get checked — not glanced at, checked — regularly.

None of this requires enterprise gear. It requires intention: the right copies, in the right places, running without human memory involved.

Tested restores: the part everyone skips

A test restore means actually pulling files — or better, a whole system — out of the backup and confirming they work. Not checking a green checkmark on a dashboard. Actually opening a patient chart from the restored copy. Actually confirming the schedule is intact.

Do it quarterly. It takes an hour or two, and it answers the only question that matters: if everything went down tonight, how long until we’re seeing patients again? Write the answer down. That number is your recovery time, and it belongs in your planning — and in conversations with your insurance carrier, who increasingly asks for it.

Downtime math for a clinic that can’t see patients

Do this arithmetic once, on paper. Take your average daily collections. Multiply by the number of days you’d be down without working systems — be honest; without tested backups, assume a week. Add payroll for those days, because your team still gets paid. Add the cost of breach notification letters if patient data was exposed, plus the patients who quietly find another practice while you’re dark.

Now compare that total to the cost of doing backups properly: isolated copies, quarterly test restores, someone accountable for checking the jobs. The math is not close. Downtime is the most expensive backup strategy there is.

What to do Monday morning

• Ask: “Where are our backups, exactly? Are any of them unreachable from our network?”
• Ask: “When did we last restore something from backup — not check the dashboard, actually restore?”
• Schedule the next test restore before you leave today. Put it on the calendar quarterly.

Frequently asked questions