How to Back Up Eaglesoft Without Losing Records or Imaging

What do you actually have to back up in Eaglesoft?

Two things, and they are not stored in the same place. Eaglesoft keeps your patient records, ledgers, scheduling, and clinical notes in a database, and it keeps your imaging and scanned documents — X-rays, photos, signed forms — in separate files and folders on disk. People lose data because they back up one and forget the other.

The database without the imaging gives you a chart that references X-rays you no longer have. The imaging without the database gives you a folder of image files with no patient context. You need both, captured from the same moment so they agree with each other.

Eaglesoft has historically run on a Sybase SQL Anywhere database engine {{VERIFY: current engine and version in your install}}, and the imaging and document store lives in its own directory tree {{VERIFY: exact imaging path on your server}}. Treat the database and the imaging as one inseparable unit for backup purposes.

Why isn't copying the files enough?

Because the live database is moving while you copy it. When Eaglesoft is open, the engine is constantly writing to the database files. If your backup tool copies those files while a transaction is half-written, you get a crash-consistent or torn copy — it may restore, mount, and then refuse to open or report corruption days later.

The fix is application-consistent capture: a method that coordinates with the database engine to flush pending writes and quiet it for an instant, so the snapshot is internally clean. This is the single most important difference between a backup that restores and one that fails. We go deeper on how this fails in the real world in Why Your Dental Backup Got Encrypted Too.

The Eaglesoft backup checklist

Here is everything a correct Eaglesoft backup includes. If any box is unchecked, you have a gap.

• Database captured application-consistently — the engine is quiesced and writes are flushed before capture, not a hot file-copy of live files
• Imaging and documents folder captured in the same pass — X-rays, photos, and scanned forms, taken from the same moment as the database so they stay in sync (this is the step people forget)
• Storage-engine consistency verified — capture accounts for the database engine's transaction and log files {{VERIFY: engine specifics}} so the restored database is internally clean
• Off-site copy — at least one copy lives somewhere a fire, flood, or theft at the office cannot reach
• Immutable copy — at least one copy is write-once and cannot be altered or deleted for its retention window, including by an admin or ransomware
• Encrypted in transit and at rest — patient data is protected on the wire and on the storage target
• Schedule matched to your RPO — back up often enough that the work you would have to re-enter after a loss is acceptable (nightly at minimum; more often for busy practices)
• Tested restore — you have restored database plus imaging onto separate hardware and confirmed Eaglesoft opens and the images line up

The two most common failures

The two boxes that go unchecked most often are imaging and tested restore. Imaging gets missed because it lives outside the database and feels like "just files" until the day a malpractice claim needs an X-ray you cannot produce. Restores get skipped because they take effort and the backup looked fine. A backup you have never restored is an assumption.

Where should the copies live?

Not only on the server, and not only on a USB drive plugged into it. If your backup sits on the same machine or the same network as the live data, a single ransomware event takes both. This is exactly how practices lose their backups along with their production data — the encrypted server also held the only backup.

That is why the off-site and immutable boxes matter so much. Off-site survives physical disasters. Immutable (write-once) survives the attacker who finds your backups and tries to delete or encrypt them. Together they are what turn a backup into something you can actually recover from. The full recovery sequence is laid out in The Dental Ransomware Recovery Playbook.

How often, and who runs it?

Nightly is the floor. Each night you do not back up is a day of charting, payments, and images you would have to reconstruct from memory after a loss. Busier practices push to more frequent capture so the gap stays small.

Who runs it matters too. An unmonitored job that silently failed three weeks ago is the worst outcome — you think you are covered and you are not. An MSP-managed approach means someone is watching the job results, alerting on failures, and periodically proving the restore works, under a HIPAA Business Associate Agreement that puts the obligation in writing. DDSArk runs Eaglesoft backups this way: application-consistent capture of the database and imaging together, encrypted, copied off-site, and held immutable.

This article is general guidance, not legal or HIPAA compliance advice; confirm your own obligations with qualified counsel.