Restore databases
Purpose
Section titled “Purpose”Replace both databases from a verified .emubackup package.
Audience
Section titled “Audience”Framework administrators responsible for recovery.
Prerequisites
Section titled “Prerequisites”A validated .emubackup, application stop/start access, and a copy of the current databases.
Procedure
Section titled “Procedure”- Validate the package in System Maintenance.
- Stop the application and keep the current databases as an additional copy.
- On Windows run
RestoreDatabase.cmd "C:\path\backup.emubackup". - For Docker, extract the validated database files into the stopped
emu-datavolume using an administrative container. - Restore the original integration secret key to
.emu-secret.keybesidedesigner.db, or toEMU_SECRET_KEY_PATH, before starting the app. - Start the app and verify login, apps, recent records, and Settings → SMTP Settings.
- Select Verify connection and send a test email. If the original key is unavailable, save the SMTP password again to encrypt it with the new key.
Never replace a live SQLite file by copying over it. Restore both databases from the same package. Do not assume .emubackup contains the integration secret key; it must be recovered separately.