Open Dental keeps your practice in a MySQL/MariaDB database. Backing it up safely means consistent database copies and images, stored immutably and off-site.
Updated
What you need to protect
Open Dental stores clinical and scheduling data in a MySQL/MariaDB database and keeps images in
a linked file store. Both must be captured together and consistently so a restore returns a
complete, working practice.
The standard to hold
Off-site: a copy away from the practice survives local disasters.
Immutable: write-once copies survive ransomware aimed at backups.
Tested: regular restores prove the backup actually works.
Key takeaways
Back up the MySQL/MariaDB database and the image store together, consistently.
A local nightly dump alone is exposed to ransomware and single-point failure.
Immutable, off-site copies plus tested recovery are the bar.
Open Dental data is PHI — your backup vendor should sign a HIPAA BAA.
Open Dental backup with DDSArk
DDSArk protects Open Dental as part of a managed, multi-site service: immutable recovery points,
off-site replication, automated test restores, and a signed BAA. See
the dental backup comparison for how the options stack up.
Frequently asked questions
How do I back up Open Dental?
Open Dental stores data in a MySQL/MariaDB database, so back up that database consistently and store the copies off-site and immutably. DDSArk runs an agent on the Open Dental server that captures scheduled, application-consistent recovery points and ships them encrypted to immutable cloud storage. Exact steps: install the DDSArk agent on the Open Dental server, point it at the MySQL/MariaDB database and image folder, and set a schedule — DDSArk takes consistent recovery points, encrypts them, and replicates them off-site to immutable storage.
What database does Open Dental use?
Open Dental uses a MySQL/MariaDB database for clinical and scheduling data, plus a file store for images. Both must be backed up together so a restore returns a complete practice. Confirm your version and image-path setup: Open Dental runs on a MySQL/MariaDB database with a separate image file store, and DDSArk backs up both together so a restore returns a complete practice.
Can I rely on a nightly local dump of Open Dental?
A nightly local dump is a start, but if it lives on the practice network it is exposed to ransomware and single-point hardware failure. Add immutable, off-site copies and verify restores.