The practice owner calls on a Monday morning: the server won't boot. The IT provider drives on-site, confirms the hard drive failed, and asks a question that determines the next three months of this practice's life: "When was the last successful backup?"

In the best case, the backup ran last night, it's stored offsite, and a new server can be restored within hours. In the worst case — which we see far too often — the backup was a USB drive plugged into the dead server. That drive either failed with the server, was encrypted by ransomware, or hasn't actually been backing up successfully since the software license expired six months ago.

70% of dental practices that lose their server without a verified backup never fully recover their patient data. They rebuild from paper records, insurance claim histories, and whatever fragments they can piece together. Some never recover at all and start from scratch.

The 3-2-1 Backup Rule for Dental Practices

The 3-2-1 backup rule is the minimum standard for any practice that values its patient data:

  • 3 copies of your data — The original data on your server, plus two backup copies. If one backup fails, you still have another.
  • 2 different storage types — Don't put both backups on the same kind of media. If your primary backup is a local NAS (network-attached storage), your second backup should be cloud-based. If both backups are USB drives, a single theft or fire takes them both.
  • 1 copy offsite — At least one backup must be physically separate from your office. Cloud backup satisfies this. So does a rotating external drive that your office manager takes home each night (though cloud is more reliable and less dependent on human memory).

Many dental practices we onboard have only one backup — a single USB drive or NAS device sitting next to the server. That's not 3-2-1. That's one copy on one media type in one location. A fire, a theft, a ransomware attack, or a power surge takes the server and the backup simultaneously.

What Needs to Be Backed Up in a Dental Practice

Not all data on your server is equally critical. Here's what matters most, in order of priority:

  1. Practice management database — Open Dental's MySQL database, Dentrix's SQL Server database, or Eaglesoft's database. This contains every patient record, appointment, clinical note, and billing transaction. Losing this is catastrophic.
  2. Imaging archive — X-ray images, panoramic images, CBCT scans, intraoral photos. DEXIS, Carestream, and other imaging systems store these as files on the server or a dedicated imaging server. A typical 10-year-old practice has 200+ GB of imaging data.
  3. Document scans and attachments — Scanned insurance cards, referral letters, consent forms, ID photos. These are often stored as attachments within the PMS or in a shared folder on the server.
  4. Financial and accounting data — QuickBooks files, payroll data, tax documents. Important for business continuity, though not as time-sensitive as patient data.
  5. Configuration and settings — Practice management software configuration, bridge settings, printer configurations, scheduled tasks. These can be recreated manually, but having them in a backup saves hours during restoration.

RPO and RTO: The Two Numbers Every Practice Owner Should Know

RPO (Recovery Point Objective) answers: "How much data can we afford to lose?" If your backup runs at midnight and your server dies at 4 PM, you've lost 16 hours of data — every appointment, chart note, and billing transaction entered that day. An RPO of 1 hour means you can lose at most 1 hour of work.

RTO (Recovery Time Objective) answers: "How long can we be down before it's unacceptable?" If your RTO is 4 hours, you need a backup system that can restore your entire server — operating system, database, imaging archive, and all — within 4 hours.

Here are realistic RPO/RTO targets by practice size:

  • Solo practice (1–3 operatories) — RPO: 4 hours. RTO: 8 hours (next business day). A solo practice can survive paper charting for a day if needed. The financial impact of longer downtime is lower because production volume is lower.
  • Group practice (4–8 operatories) — RPO: 1 hour. RTO: 4 hours. With multiple providers seeing patients simultaneously, the cost of downtime is significant. An hour of lost data means re-entering a full morning of chart notes.
  • Multi-location practice — RPO: 15 minutes. RTO: 2 hours. High-volume operations can't afford data loss or extended downtime. Real-time replication to a standby server, combined with cloud backup, is appropriate here.
Ask your IT provider: "What is our current RPO and RTO?" If they can't answer, they haven't defined a disaster recovery plan for your practice. That's a problem.

Testing Your Backup: The Step Everyone Skips

A backup that hasn't been tested is a hope, not a plan. Testing means actually restoring your data to a separate system and confirming it works. Here's what a real backup test looks like:

  1. Restore the practice management database to a test machine. Open Open Dental or Dentrix on that machine and confirm you can see patient records, appointments, and chart notes from the backup date.
  2. Restore a sample of imaging data and confirm the images open correctly in the imaging software.
  3. Document the restore time — how long did it take from "start restore" to "system usable"? This is your actual RTO, not your theoretical one.
  4. Document any issues — missing files, corrupt database tables, software that won't activate on the restored machine. These issues need to be resolved before a real disaster, not during one.

Test quarterly at minimum. Monthly is better. CyberCore monitors backup job status — success, failure, warnings, completion time, and data volume — on every backup cycle. When a backup fails or completes with warnings, the alert fires immediately, not when you discover the problem during a crisis.

Ransomware-Proof Your Backups

Ransomware specifically targets backups. The attackers know that if they encrypt your backups along with your live data, your only option is to pay. Here's how to protect your backups from ransomware:

  • Air-gapped or immutable backups — Store at least one backup copy in a location that cannot be accessed from your network. Cloud backup with immutability (the provider locks stored data so it cannot be modified or deleted for a set period) is the most practical solution for dental practices.
  • Separate credentials — The account that runs your backup should not be the same account that your staff uses to log in. If ransomware compromises a staff account, it shouldn't be able to access backup storage.
  • Versioned retention — Keep 30 days (minimum) of backup history. If ransomware encrypts your files on Monday and you don't discover it until Wednesday, your most recent backup contains encrypted data. You need to restore from Saturday's backup — and that only works if you have version history going back that far.

Build Your Backup Plan This Week

You don't need to overhaul your entire IT infrastructure. Start with these three steps:

  1. Verify your current backup — Ask your IT provider to show you the last 7 days of backup job results. Look for failures, warnings, or missing days. If they can't show you this, your backup isn't being monitored.
  2. Test a restore — Schedule a backup restore test. Restore the Dentrix or Open Dental database to a test workstation and confirm it opens. Time the process. That number is your real RTO.
  3. Add a second backup destination — If you only have a local backup, add a cloud backup. If you only have cloud, add a local backup. Get to 3-2-1 before your next Monday morning surprise.

Your patient data is irreplaceable. The backup strategy that protects it should be tested, monitored, and built to survive the worst scenarios — not just the convenient ones.