We are using an External (ODBC) database to store journal entries. This generally works well but occasionally the connection will be lost (e.g. the server is restarted or there is a network issue).
When the connection is broken my expectation was that the journal would revert to using the Embedded (SQLite) database and then resync once the ODBC connection was available again. This does not seem to be happening and we end up with gaps in our journal.
Is there something I need to change within our settings?
Thanks
Edit: the records are logged into the SQLite database but not syncing back. I think the issue may be that there are three duplicate records between the two databases.
If the external journal database becomes unavailable, the server will automatically fall back to the embedded SQLite journal. However, switching back to the external journal does not happen automatically. You need to manually re-enable the external journal from the server’s web console under the Journal tab.
Any records that were written to the embedded journal during the failover won’t sync back on their own. If you need those entries in the external database, they must be manually copied over once the external connection is available again.
To clarify, a journal record can never be duplicated in both internal and external databases. Records always go either into one, or the other. Therefore, it should be relatively straightforward to copy records from the internal database to the external - there will be no overlap in IDs.