Saga — how to back up your database correctly (and how to restore it)
Losing your Saga database means losing years of accounting history. Here are 3 backup methods and how to test that your restoration actually works.
Mihai Istrati — CTO Azuvio · 2026-05-21 · 6 min · ERP & Integrations
Why a Saga backup is more important than you think
The Saga database contains: your customised chart of accounts, 5+ years of records, filed tax returns, VAT configurations, and templates. Losing it means an inability to respond to tax authority audits (legal document retention for 10 years is mandatory — e.g. under Art. 25 of the Fiscal Code in Romania or similar EU statutory requirements).
Real incidents we have encountered: HDD failure, ransomware, accidental deletion, Windows updates corrupting the database, or incorrect formatting when changing computers.
What you must include in your backup
The Saga database is usually located in `C:\SAGA\` (or D:\SAGA, or wherever you installed it). You must copy:
`\DATE\` or `\BAZA\` folder — the data files (`.dbf`, `.cdx`, `.fpt`)
`\CONFIG\` folder — user configurations
`\TEMPL\` folder — print templates, customised invoices
`\ARHIVA\` folder — scanned attached documents
If you manage multiple companies in Saga, each has its own folder — back up all of them.
Method 1 — Native backup from Saga (Recommended)
Step 1: In Saga, go to the Service → Salvare bază de date (or «Sistem → Backup» in newer versions).
Step 2: Choose the destination — IMPORTANT: DO NOT save it on the same HDD as the database. Use a second HDD, a USB stick, or better yet, a network share.
Step 3: Saga creates a `.zip` or `.bak` file with the date in the name (e.g., `SAGA_2026-05-21.zip`).
Recommended frequency: Daily for active companies, weekly for those with low volume.
Method 2 — Automated backup with a script (For larger firms)
For accountants managing 5+ companies, create a Windows Task Scheduler script that runs daily at 23:00:
`backup_saga.bat` script:
```
@echo off
set DATA=%date:~-4%-%date:~3,2%-%date:~0,2%
xcopy C:\SAGA\*.* D:\Backup_Saga\%DATA%\ /E /I /Y
powershell Compress-Archive -Path D:\Backup_Saga\%DATA% -DestinationPath D:\Backup_Saga\Saga_%DATA%.zip -Force
rmdir /S /Q D:\Backup_Saga\%DATA%
```
Configure Task Scheduler to run it daily. Add an automatic cloud upload (OneDrive, Dropbox, Google Drive) — see below.
Method 3 — Cloud backup (The most secure)
Local backup does not protect you from: theft, fire, or ransomware that encrypts the entire HDD. Cloud solutions:
OneDrive / Google Drive / Dropbox: free 5-15GB, sufficient for a standard Saga firm. Set the `Backup_Saga\` folder to sync automatically.
Backblaze / Acronis Cyber Protect: 7-15 USD/month, automated encrypted backup + versioning (keeps the last 30-90 days).
Personal NAS (Synology, QNAP): 300-800 € investment, local daily backup + cloud sync — the professional solution for high-volume firms.
Critical: The Saga backup contains PERSONAL DATA (customers, employees, IDs). Under GDPR: it must be encrypted with limited access. DO NOT put it on a public Google Drive folder.
How to test that restoration actually works
An untested backup = a non-existent backup. Follow these steps:
1. Once per quarter, copy a recent backup to a test computer (or VM).
2. Restore in Saga: Service → Restaurare bază de date → select the file.
3. Open a random month, check a few invoices, the trial balance, and the journal.
4. If it works — good. If not — investigate now, not 6 months later when your production environment fails.
For high-volume companies — professional alternatives
Saga is built for local deployment or an on-premise server. For an accountant managing 20+ companies, daily manual backup is a constant source of risk. Modern solutions:
Saga on a server with centralised backup (RAID 1 + encrypted daily backup to a secondary server)
SaaS Layer over Saga (Azuvio aggregates operational data in the cloud with automatic backup, while Saga remains local only for fiscal and statutory reporting)
Conclusion
Backing up Saga is a legal requirement but also vital for business continuity. Minimum: daily native backup + copy to another HDD + weekly cloud sync. For large firms: automated scripts + NAS + quarterly restoration tests. See migrating Saga to a new server if you need to move the database without losing any data.