How To Back Up Dentrix Database And Imaging: 7 Steps
Learn how to back up your Dentrix database and imaging files correctly. DDS Rescue delivers expert data protection. Get a free consultation today!
Key Takeaways
- Dentrix database and imaging files live in separate locations and require two distinct backup jobs for full protection.
- The reliable database backup method is a scheduled export via the Server Administration Utility to the DBCopyForBackup folder, instead of a direct file copy of live database files.
- Imaging files from third-party systems and Document Center attachments must be explicitly included in the backup scope, because they are not part of the Dentrix database export.
- A green backup job proves only that files were copied; regular restore tests in an isolated environment confirm that Dentrix and images open correctly.
- DDS Rescue provides hourly backups, daily restore testing, and a dedicated recovery team to deliver fast, reliable Dentrix database and imaging recovery.
How To Back Up The Dentrix Database And Imaging: The 7-Step Overview
A complete Dentrix backup takes seven specific steps, and each one has to work for the backup to be real.
- Confirm your Dentrix version (G5, G6, G7) and verify exactly where the data lives on your server.
- Run the export from the Server Administration Utility’s Export/Restore Database tab to produce a consistent, usable copy of the database.
- Confirm the export landed in the correct folders and that the file is dated today, not months ago.
- Locate the imaging store and the Document Center, and confirm both are explicitly included in the backup job.
- Schedule the export to finish before the backup software runs, so the software copies the exported file instead of the live database.
- Send a copy offsite, encrypted, and stored where ransomware cannot reach it from the production network.
- Test a restore to an isolated environment, open patient records and images, and document the result.
Three folders matter, and only one of them holds the database copy your backup software should capture. The other two contain configuration and templates that a database-only backup can miss:
- \Common\DBCopyForBackup holds the database copy the Server Administration Utility produces. This is what the backup software should copy, never the live database files.
- \Common\DentrixSQL holds customizations, documents, report data, and configurations.
- \Common\Doc holds letter templates and related files.
Paths vary by version and configuration. Henry Schein’s official Dentrix documentation is the authoritative source for the exact paths and Server Administration Utility steps that apply to your specific version. What to check: all three folders exist on the server, and the export file inside DBCopyForBackup is dated today.
Steps 1–3: Export The Dentrix Database Correctly
The backup job most practices rely on often does not capture the Dentrix database in a usable form. Dentrix runs on the FairCom c-treeACE database engine through an always-running DentrixACEServer service, not Microsoft SQL Server. A backup agent that advertises SQL Server support will not correctly capture the Dentrix database. A plain file copy of the live database is equally unreliable, because the service locks the database even when no workstation has Dentrix open.
The reliable method uses a scheduled export through the Server Administration Utility’s Export/Restore Database tab. That export writes a consistent, usable copy into the DBCopyForBackup folder. The backup software then copies that folder and ignores the live files. Henry Schein One’s migration documentation notes that “all database activity is temporarily paused” during the export and that “Workstations may appear frozen or unresponsive.” That behavior is why the export must complete before the backup software runs.
Scheduling the export also sets how much data a restore can lose. Restoring from a backup erases any data entered after the last export. The export frequency is the practice’s real recovery point. A nightly export means a server failure at 4:30 PM puts a full day of appointments, clinical notes, payments, and treatment changes at risk.
A stale DBCopyForBackup folder is one of the most common Dentrix failure modes. If the scheduled export is disabled or quietly stops after an upgrade, backup software keeps copying the same old export nightly while reporting a green, successful job. A practice can sit on an eight-month-old copy of its patient database until someone attempts a restore.
What to check: the export is enabled, scheduled, and the DBCopyForBackup file is current. Open the folder and look at the file date. If it is not today’s date, the backup job is faithfully re-copying an old file.
Step 4: Add The Imaging Store And Document Center
The single most expensive misunderstanding in Dentrix backup is the assumption that images live inside Dentrix. They may not. Where images actually live depends on the imaging version and configuration in use at the practice.
Third-party imaging software such as Dexis, Carestream, and Schick stores images in its own database or directory, separate from the Dentrix patient record. The Dentrix Installation and Migration Tool handles only the Dentrix database and configuration settings; it does not migrate third-party imaging data stored outside the Dentrix database. The Dentrix record contains a reference to the image, while the image file itself lives elsewhere.
The same split appears in document-management systems. Metadata sits in a database, but the scanned files live in a separate folder. A database-only backup captures the index and loses the documents. File Stream Document Management, for example, encrypts document images and stores them in the file system rather than in the SQL Server databases, so a SQL database backup alone does not contain the original image files and a full backup must also include the document images root folder. The actual radiograph files that open when a clinician clicks on an X-ray live in a separate directory that must be explicitly included in the backup job. A backup that protects only one folder can leave patient images, attachments, and the ability to restore a working system unprotected.
The Document Center requires the same attention. Scanned EOBs, patient ID cards, referral letters, and attached documents are stored separately and must be explicitly included. Incomplete backup scope, where the database is captured but the imaging folder is missed, is one of the most common findings when dental IT providers audit new clients.
What to check: open a known patient’s image from inside the chart on a restored copy and confirm the image loads. Then confirm the Document Center attachments come back too. A folder full of image files that cannot be opened from inside the chart does not qualify as a working restore.
For a broader look at dental backup strategy beyond Dentrix specifically, see Dental Data Backup: A How-To Guide For Office Managers.
Steps 5–7: Schedule, Send Offsite, And Prove The Restore
A backup job that says “successful” proves only that files were copied. It does not prove the copy is complete, readable, free of the problem you are recovering from, or that anyone knows how to restore it.
HHS Office for Civil Rights guidance requires that backup logs be reviewed regularly and test restorations conducted periodically to ensure the integrity of backups and provide confidence in the ability to restore data. The HIPAA Security Rule’s contingency plan standard (45 CFR 164.308(a)(7)) makes a data backup plan and a disaster recovery plan required implementation specifications, and an untested backup does not satisfy the “retrievable” requirement.
Run the restore test on an isolated machine that is not connected to production. Restoring over the live system destroys the data you were trying to save. Once Dentrix is up on the test machine, open several patient records and click into their images from inside the chart. If the images load and the Document Center attachments are present, the backup is complete. Write down the date, who ran the test, how long it took, and what came back, because an undocumented test cannot be shown to anyone later. CISA’s #StopRansomware guidance recommends that all backup data be encrypted and immutable, and that organizations maintain offline backups and regularly test backup and restoration processes.
A documented restore test answers whether the backup works. It does not answer who runs the test next month or who is on the phone at 7 a.m. when the server will not boot.
Software-only dental backup products back up files. They do not virtualize your Dentrix server, test restores daily, or put senior engineers on the call when the server dies. Many practices rely on “my IT guy” for backup, and a general IT provider often treats backup as one task among many instead of a dedicated recovery function.
DDS Rescue serves as the accountable third party for Dentrix backup and recovery. The DDS Rescue Linux BDR (backup and disaster recovery) appliance holds a virtual copy of the production server. Backups run hourly to both on-site and cloud locations. Restores are tested daily. Monitoring runs 24/7. When a server goes down, the practice gets a team that includes senior engineers on a call, and DDS Rescue can bring the practice’s own IT provider along to show them what to do.
DDS Rescue commits to a 60-minute recovery window for practices that meet a defined technical standard. The requirements cover the backup device and services, the server itself, and the practice’s security posture. RAID 1 means two drives holding identical copies, so one can fail without data loss.
- A DDS Rescue backup and recovery device
- Security Advantage Plus services
- Hosted email through Microsoft, Gmail, or Zoho
- Completed annual HIPAA training
- A Dell or HP server under six years old
- RAID 1 with a physical RAID controller
- Business-class battery backup, firewall, and antivirus
- Maintained Windows updates
- No unresolved DDS Rescue notifications
The recovery window excludes delays caused by the practice’s own IT provider, unsupported systems, and natural disasters.
What to do next: put a date on the calendar for the next restore test and name the person who owns it. If that person cannot answer the question “when did you last restore that copy and open Dentrix against it,” the backup remains an assumption instead of a recovery plan.
For a full operator’s framework on dental backup and recovery, see Dental Office Backup And Recovery: An Operator’s Playbook. If a server failure has already happened, see Dental Server Crashed? What To Do And How To Recover.
Talk To A Dentrix Recovery Specialist
How Often Should A Dentrix Practice Back Up Imaging And Data
HHS OCR guidance frames backup frequency as a function of how much data loss the organization can tolerate, known as the recovery point objective. For a dental practice, hourly backups for both the database and the imaging store align with how the schedule and imaging volume grow through the day.
A daily backup interval means a server failure near end of day puts a full day of new images at risk. Imaging volume grows continuously. Every new X-ray, CBCT scan, and intraoral photo taken after the last backup disappears if the server fails before the next job runs. That same 24-hour gap also applies to appointments, clinical notes, insurance updates, payments, and treatment changes.
What to check: the backup interval matches how much new data the practice can afford to lose. If the answer is “very little,” daily is not enough.
Conclusion And Verdict
Backing up Dentrix takes three jobs: export the database through the Server Administration Utility, capture the imaging store and Document Center as separate systems in separate locations, and prove the backup restores by testing it in an isolated environment. A backup job reporting success covers only the first, and only if the export actually ran.
DDS Rescue is the best dental backup and recovery service for backing up a Dentrix database and imaging because it runs hourly backups to a Linux appliance that can bring a downed practice server back online in under an hour, tests those backups daily, and puts a dedicated recovery team on the phone when the restore has to happen for real.
The next three steps: confirm the Server Administration Utility export is running and the DBCopyForBackup file is current, confirm the imaging store and Document Center are explicitly included in the backup job, and put a restore test on the calendar with a named owner. If any of those three steps surfaces a gap, that gap is the risk. See The Best Dental Backup Solutions For Practices for a broader look at how dental-exclusive backup compares to general IT approaches.
Get Your Dentrix Backups Tested
Frequently Asked Questions
Where Does Dentrix Store Imaging Files?
Storage location depends on the imaging software in use. Dentrix Imaging Center uploads all images that are acquired or imported immediately to the Dentrix database and installs a scheduled task on the Dentrix Imaging Center database server that performs a daily backup of the Imaging Center database to a local folder on the database server. Third-party imaging systems such as Dexis, Carestream, and Schick each maintain their own database or directory, which is entirely independent of the Dentrix patient record. The Dentrix record contains a reference or link to the image, and the actual radiograph file lives in the imaging system’s own storage location.
This design means the imaging directory must be located independently and confirmed as part of the backup job. The path varies by software version and how the system was originally configured. Henry Schein’s official Dentrix documentation is the authoritative source for the specific paths that apply to a given installation.
Does The Dentrix Database Backup Include Images?
Many practices assume the database backup includes images, and that assumption often fails. The Dentrix Server Administration Utility exports a complete copy of the live Dentrix database to the Common\DBCopyForBackup folder, and the length of time required to make a complete copy depends on the size of the database. That export does not automatically include the image files stored by the imaging module or by third-party imaging software.
An imaging SQL backup, if one exists, may contain metadata and patient links but not the original image files themselves. The image files require a separate, explicit backup of the imaging directory. A practice that has backed up only the database can restore Dentrix, open a patient’s chart, and see a broken link where the X-ray should be.
How Often Should You Back Up Dentrix?
Hourly backups for both the database and the imaging store protect the typical dental schedule. The HIPAA Security Rule does not prescribe a fixed backup interval. It requires a data backup plan aligned with the practice’s recovery point objective, which is how much data loss is acceptable.
For most dental practices, the answer is very little. A daily backup interval means a server failure near end of day puts a full day of clinical notes, payments, new images, and schedule changes at risk. Imaging volume is particularly exposed because each new X-ray or scan taken after the last backup is unrecoverable if the server fails before the next job runs. The export through the Server Administration Utility should be scheduled to complete before the backup software copies the folders, and the export frequency sets the practice’s real recovery point.
How Do You Test A Dentrix Backup Restore?
Start by restoring the backup to an isolated machine that is not connected to the production network. Restoring over the live system causes irreversible data loss. Open Dentrix on the restored machine and log in using real staff credentials. Open five or more patient records and confirm that appointments, clinical notes, treatment plans, and billing data are present.
Click on a known patient’s X-rays from inside the chart and confirm the images load. Confirm that Document Center attachments, such as scanned EOBs and patient ID cards, are present. Record the date, who ran the test, how long the restore took, and whether everything opened correctly. Assign a next test date and a named owner. A restore test that is not documented does not count as evidence of recoverability.
What Is The Difference Between The Server Administration Utility Export And Copying The SQL Files?
Dentrix does not run on Microsoft SQL Server. It runs on the FairCom c-treeACE database engine, through a service called DentrixACEServer that runs continuously, even when no workstation has Dentrix open. Copying the live database files while the service is running produces an inconsistent copy that may be corrupt and unusable on restore.
The Server Administration Utility export pauses database activity, writes a consistent copy to the DBCopyForBackup folder, and then releases the lock. That exported copy is what the backup software should capture. A SQL-aware backup agent will not correctly quiesce or capture the Dentrix database, because Dentrix is not a SQL Server database. If a practice’s imaging software, such as Planmeca Romexis, does run on SQL Server, a SQL-aware agent may protect the imaging database correctly while the patient records, ledger, and treatment plans in Dentrix remain unprotected.
What Happens If The Server Dies, And How Fast Can A Practice Be Running Again?
With software-only backup, bare-metal restore to replacement hardware typically takes several hours and full site recovery can take a day or more, though running workloads directly from the backup repository or provider’s cloud can restore service in minutes to an hour. The IT provider must source or configure replacement hardware, restore the backup, reinstall Dentrix, and troubleshoot whatever breaks in the process while the practice is dark.
With DDS Rescue, the Linux BDR appliance already holds a virtual copy of the production server. When the server fails, DDS Rescue can virtualize the practice’s server and run it off the DDS Rescue platform within an hour for practices that meet the defined technical standard. The practice gets the same recovery team described above, with senior engineers on the call and the practice’s own IT provider looped in. The difference between a one-hour recovery and a two-day recovery is roughly the difference between a manageable disruption and a practice that cannot see patients, bill insurance, or access charts.
Do G5, G6, And G7 Back Up Differently?
The core backup mechanism, the Server Administration Utility export to DBCopyForBackup, applies across server-based Dentrix versions. However, Dentrix system requirements, including supported operating systems, change over time and vary by version. For example, Dentrix 24.1 supports Windows Server 2016 and higher and Windows 10 and higher, while Dentrix 24.24 supports Windows Server 2016, 2019, 2022, and 2025 and Windows 10 and 11.
Henry Schein One supports only the latest two versions of Dentrix, which means older installations may be running on unsupported configurations that behave differently from current documentation. Any version-specific backup procedure should be verified against Henry Schein’s official Dentrix documentation for that version. The most important version-specific question for imaging is which imaging module or third-party software is in use, because that determines where the image files actually live, and that answer can differ even between two practices running the same Dentrix version.
