Backup and Restore
Backup and Restore
All Transbox business data — projects, files, segment translations, memories, termbases, translation records, chats, parse results — lives in one local SQLite database. Backing up means copying that file; restoring means replacing it with a backup.
Automatic Backups
- Trigger: checked at every launch; if today's backup is missing, it is created immediately
- Frequency: at most one per day
- Retention: the last 30 days of daily backups; older ones are pruned
- Naming:
.client-sqlite-YYYY-MM-DD.db - Location: the application data directory (on Windows, under
%APPDATA%)
No configuration is needed. Automatic backups only cover "some day within the last 30 days"; export manually for long-term archives.
Manual Export
Settings → Network & advanced → Data backup → Export backup. Choose a source:
| Source | Meaning |
|---|---|
| Current data | A copy of the database in use right now, with the latest state |
| Pre-import safety copy | The original database captured during the last import, for rollback |
| Daily backup | Any automatic backup from the last 30 days |
Pick one, choose a destination, and you get a timestamped .db file. Keep it on a network drive, an external disk or in version control.
Restoring from a Backup
Import backup overwrites all data on this device, so it is guarded by three confirmations:
- It shows the file name, size, backup time and a content summary (projects, memories, termbases, translation records, chats)
- You must type
confirm - The main process shows a final system-level confirmation
After that, the backup is staged and the database is replaced at the next launch. The current database is first copied to .client-sqlite.pre-restore.db, so a mistaken import can be rolled back.
Database Files
| File | Purpose |
|---|---|
.client-sqlite.db | Main business database |
.client-sqlite-fts-5.db | Full-text search index (derived; can be rebuilt from the main database) |
.client-sqlite.pending-restore.db | Staged restore file, swapped in at launch |
.client-sqlite.pre-restore.db | Safety copy created before an import |
.client-sqlite-YYYY-MM-DD.db | Daily automatic backup |
Moving to a New Device
- Old device: Export backup → Current data, save the
.db - Copy the file to the new device
- Install Transbox and launch it once
- Import backup with that
.db, confirm and restart - Verify projects, memories, termbases and settings
Best Practices
- Export at milestones: after a delivery, after a large import
- Store in more than one place: local plus cloud or external disk
- Name recognizably: keep the date, add a project tag if useful
- Verify occasionally: import a backup on a test machine to confirm it works
- Export before importing: always take a fresh copy before an overwrite
Notes
- Import cannot be undone except via the retained pre-restore copy
- A restart is required for the import to take effect
- Single instance: make sure only one client instance runs, or file locks may block the swap
- Disk space: the database grows with your corpora — check free space before exporting
- Versions: prefer importing an older backup into the same or a newer version
FAQ
Q: Where are the automatic backups?
A: In the application data directory (under %APPDATA% on Windows). You do not need to find them by hand — pick the daily backup directly in the export dialog.
Q: Can I turn automatic backups off?
A: There is no switch; it is default behaviour. One file per day with 30-day retention keeps the footprint small.
Q: I imported a backup but nothing changed.
A: The database is replaced at the next launch. If "Restart now" did not help, check for other running instances.
Q: Can I restore only memories?
A: No — import replaces everything. Use Memory → Import (TMX / SDLTM / Excel) to move corpora individually.
Q: The backup file is corrupt.
A: Try an earlier daily backup or a manual export. As a last resort, rename .client-sqlite.pre-restore.db to the main database name and launch.
Q: Does a backup contain API keys?
A: Yes — the database holds all local configuration, so keep backup files private.