⚠️ Error during database migration after config import or web update – Brevis.one

🧩 Issue: “Database Migration” Gets Stuck

After a firmware update via the web interface or importing an older configuration , the following message may appear:

“Database migration”

The loading bar does not disappear, and the gateway remains stuck in this state. In most cases, normal access is no longer possible.

🔍 Possible Causes

Outdated configurations (especially from versions prior to 22.00 )
Structural changes in the database due to new system base (eg migration to Debian 11+ )
Legacy data that cannot be migrated , such as:
- Historical message records
- Deprecated routing entries
- Inconsistent rule definitions

These issues prevent the migration script from completing successfully.

📉 Typical Symptoms of Failed Migration

Sent or received messages are not displayed
The “Message Status” view remains empty
The web interface becomes unresponsive or shows intermittent errors
High CPU load; services like Apache/PHP hang indefinitely

👨‍🔧 Current Status

As of firmware version 23.02 , this issue is largely resolved.
The migration logic has been revised and is now more tolerant of legacy data structures .

✅ Recommended Immediate Action (Workaround)

🔐 Create a Backup Before Reset

Export the license key
Backup the address book (as a CSV file)

🧰 Perform a Factory Reset

Use a console cable (eg USB-to-serial) and access the device via PuTTY
Run the factory reset command in the console

♻️ After Reboot:

Re-import the license key
Re-import the address book

❗ Do NOT import the old configuration!
→ This is the only way to ensure that corrupted legacy data is not reintroduced into the system.

🔁 Alternative Solutions (Advanced Users Only)

🔄 Reinstall Using a Recovery Image

Use the latest recovery image provided by the manufacturer
Fully reinstall the gateway
Manually recreate the configuration

📌 Recommendations for Future Migrations

🔄 Preparation and Version Awareness:

Only import configurations if the major version is identical
→ We regularly announce version jumps in our newsletter

For major version changes:

Recreate the configuration manually via the new web interface
Avoid importing old backups directly

Before Any Import:

Back up the license key separately
Export the address book individually

💡 Bonus Tip for Admins

Consider using an automated backup script to regularly back up key configuration data, including:

License file
Address book

This allows for fast and controlled recovery in the event of failure – without relying on outdated full backups.

Related to