Dentrix Backup, Done Properly: How to Protect the One
Information Technology Solutions for Dentists and the Dental Industry. Serving the GTA and Southern Ontario.
Dental I/T, Dental Information Technology, Network Security, Toronto, GTA, Dental, Network, I/T, Information Technology, Computer, Data, Abeldent, Dentrix, LiveDDM, Patterson Dental, Henry Schein, K-Dental, Sinclair Dental, Schick CDR, Dexis, Carestream, Carestream Dental, Digital Radiography, X-ray, Dental X-ray, Dental Software Support, Software
19338
bp-nouveau,wp-singular,post-template-default,single,single-post,postid-19338,single-format-standard,wp-theme-bridge,wp-child-theme-bridge-child,theme-bridge,woocommerce-no-js,ajax_fade,page_not_loaded,,columns-4,qode-child-theme-ver-1.0.0,qode-theme-ver-10.0,wpb-js-composer js-comp-ver-4.12,vc_responsive

Dentrix Backup, Done Properly: How to Protect the One Database Your Dental Practice Cannot Afford to Lose

A dental practice management database depicted as a secure vault at the centre of a dental office network, with protected backup copies flowing to a local server and an off-site cloud, representing a properly backed-up Dentrix database

Dentrix Backup, Done Properly: How to Protect the One Database Your Dental Practice Cannot Afford to Lose

Ask a dental practice what it would lose if the building caught fire overnight, and most owners will mention the equipment, the chairs, the sensors. Ask what it would lose if the Dentrix database vanished and could not be restored, and the room goes quiet. That one database is the practice: the schedule, the clinical charts, the treatment plans, the ledgers, the insurance history, the recall lists. Lose it without a working backup and you do not have a bad week — you have a practice that cannot confirm tomorrow’s appointments, bill yesterday’s work, or prove what care a patient has received.

Here is the part that catches practices out. A Dentrix backup can run every night, report success every morning, and still restore absolutely nothing on the day you need it. “We have a backup” is not the same as “we have a backup that comes back.” This is a product-specific problem, and it deserves a product-specific answer.

A dental practice management database depicted as a secure vault at the centre of a dental office network, with protected backup copies flowing to a local server and an off-site cloud, representing a properly backed-up Dentrix database
Dentrix is the single database that runs the practice. Protecting it means more than one copy, kept in more than one place, and proven to restore.

Why Dentrix is not a normal file-copy backup

Ordinary documents — a spreadsheet, a PDF, a folder of photos — are easy to back up because they sit still. You can copy them and the copy is complete. Dentrix is different. It stores your patient data in a specialized database that is always open whenever the software is running. Its files are locked by the application and are being written to constantly as the front desk schedules, the operatory charts, and the billing posts throughout the day.

If a backup tool simply tries to drag those live, locked database files to a USB drive or a network share while Dentrix is in use, it grabs them mid-change. The result is a copy that is internally inconsistent — half of one transaction, none of another — and when you try to restore it, the database refuses to open or opens corrupt. The backup job, meanwhile, happily reported “completed.” That gap between “the job finished” and “the data is actually usable” is the single most common reason a practice discovers, at the worst possible moment, that it has months of backups and not one it can restore.

A backup being copied from a live, in-use database whose files are locked and changing, resulting in a backup copy shown as cracked and incomplete, illustrating how copying an open database produces a corrupt backup
The hidden failure: copy a live, open database while the software is running and the backup can arrive cracked and un-restorable, even though the job reports success.

Back it up the way a database wants to be backed up

The fix is to never back up Dentrix as if it were a pile of ordinary files. There are two legitimate approaches, and good backup setups use one of them:

  • Quiesce the database first. Stop the Dentrix server service (so the files are closed and consistent), take the copy, then restart it — typically scheduled overnight when no one is working.
  • Use application-aware or snapshot-based backup. Backup software that is database-aware, or that uses the operating system’s Volume Shadow Copy Service (VSS) to take a consistent point-in-time snapshot, can capture an open database correctly without manually stopping it. This is how most professional backups handle live databases.

What matters is that the method produces a consistent copy of the database, not a smear of files caught mid-write. If you cannot say which of these two methods your current backup uses, you do not yet know whether your Dentrix backup is real.

Do not forget the imaging — it often lives somewhere else

A dental record is not only the Dentrix database. The radiographs and photos captured through DEXIS or another sensor system are frequently stored in a separate location — a different folder, drive, or even a different server — from the main Dentrix database. It is entirely possible to have a flawless backup of the practice-management database and no backup at all of the images attached to it, or vice versa. When you plan a Dentrix backup, map both: where the database lives, and where the imaging lives, and make sure one job covers both. A patient chart with no X-rays is only half a record, and in Ontario the images are part of the record you are legally obligated to retain.

One copy is not a backup: apply 3-2-1, with something offline

Even a perfect nightly backup sitting on a drive plugged into the server is dangerously fragile, and the reason is ransomware. Modern attacks no longer just encrypt the workstation in front of a staff member; they deliberately seek out and encrypt every backup they can reach first, precisely so you have no choice but to pay. A backup NAS on the same network is a prime target — we covered exactly this when ransomware began hunting Synology backup devices used by practices. If your only backup is always connected and always reachable, assume an attacker can reach it too.

The durable answer is the long-standing 3-2-1 rule: at least three copies of your data, on two different kinds of media, with at least one kept off-site and, ideally, offline or immutable. The off-site, disconnected copy is the one that survives a fire, a flood, a stolen server, or a ransomware crew that encrypted everything plugged in. For a dental practice that usually means a properly configured cloud backup, or rotated media taken off the premises, in addition to the fast local copy you would use for an everyday restore.

A 3-2-1 backup concept showing three copies of data on two different media with one copy kept off-site, applied to a dental practice's records
The 3-2-1 rule: three copies, on two kinds of media, with one kept off-site and out of reach.
Ransomware spreading across a network and reaching a connected backup drive and NAS, with one air-gapped off-site backup kept safely out of its reach
Modern ransomware hunts the backups first. A copy that is always connected can be encrypted too; an offline or off-site copy is what survives.

The step everyone skips: prove the restore

If you take only one thing from this article, take this: a backup is a theory until you have restored it. The job reporting success tells you a file was written. It tells you nothing about whether that file will reopen as a working Dentrix database. The only way to know is to periodically restore a backup onto a separate, isolated machine and confirm the database actually opens, the patients are there, and the images resolve. We have made this point before because it is the one that saves practices — your backups are only as good as your last test restore. A quarterly test restore is cheap insurance against the most expensive surprise in the building.

The same discipline applies to the servers Dentrix runs on. A practice that cannot bring its server back — whether from a failed update, a bad patch that will not boot, or a hardware failure — needs a tested recovery path, not just a data copy. Backups and the ability to rebuild the machine they run on are two halves of the same plan.

And no, the vendor is not quietly handling this

It is tempting to assume that a company as large as the one behind Dentrix must be protecting your data for you. The responsibility for backing up the Dentrix database on your server is yours, not the vendor’s — and it is worth remembering that even Dentrix’s own parent company, Henry Schein, was itself knocked offline by ransomware and hit repeatedly in a single stretch. Large vendors get breached. “Someone bigger is surely taking care of it” is not a backup strategy; a tested 3-2-1 plan that you control is.

A Dentrix backup readiness check

You do not need to be the one running the backup to ask the questions that reveal whether it is trustworthy. Put these to whoever manages your IT:

  • Does our backup use a database-aware or snapshot method, or does it stop the Dentrix service — rather than copying live, open files?
  • Does the backup include both the Dentrix database and the imaging/X-ray data, wherever each one actually lives?
  • Do we have at least three copies, on two types of media, with one off-site and disconnected or immutable?
  • When did we last perform a full test restore onto a separate machine and confirm the database opened with patients and images intact?
  • If ransomware encrypted every connected device tonight, which specific copy would we restore from — and is it out of the attacker’s reach?

If any answer is “I’m not sure,” that is the finding, and it is far better to find it today than during a recovery. A Dentrix backup that has never been restored is not a safety net; it is a hope.

At Compudent Systems, making sure a practice’s Dentrix database and imaging are backed up with a method that actually restores — consistent, off-site, ransomware-resistant, and tested on a schedule — is core to keeping a dental office running. If you cannot confidently answer the questions above, contact Compudent Systems for a backup and disaster-recovery review, and we will verify that the one database your practice cannot lose will come back when you need it.


Sources & further reading:

Related Reading



Contact us today - How can we help you?