Restore databases
Purpose
Section titled “Purpose”Restore the Full, Data, Designer, or Fonts components declared by a verified .emubackup package.
Audience
Section titled “Audience”Framework administrators responsible for recovery.
Prerequisites
Section titled “Prerequisites”A validated .emubackup, Framework Administrator access, and a separate copy of the current databases and integration secret key.
Procedure
Section titled “Procedure”- Open System Maintenance, upload the package, and select Preview restore.
- Review the manifest, selected components, checksums, SQLite integrity result, version, and warnings.
- Keep a current Full backup and a separate copy of
.emu-secret.keyorEMU_SECRET_KEY_PATH. - Type
RESTOREand confirm. Keep the page open while the app stops and reconnects. - Sign in again if Data was restored; user, security, and session records now match the backup.
- Verify apps, recent records, Designer customizations, reports/fonts, and Settings → SMTP Settings for the components restored.
- Verify the SMTP connection and send a test email. If the original key is unavailable, save the SMTP password again to encrypt it with the current key.
On the supported Docker deployment, the updater sidecar stages the validated files, stops the app, replaces only the selected components, restarts it, and performs a health check. If replacement or restart fails, it restores the pre-restore files and attempts to restart the previous state.
Never replace a live SQLite file manually. Do not mix components from different backup generations unless you have verified their compatibility. A .emubackup never contains the integration secret key; recover it separately.