In the event that you need or want to revert to an earlier back-up of a database for whatever reason, the journal file associated with the database that is being replaced will obviously have more transactions in it compared to the back-up database. In other words, all transactions in the journal file that were completed after the back-up database was created will not have been run in the back-up database. Therefore, when you put the back-up database in production, you will first need to remove the extra transaction entries from the journal file. This article describes how to sync the journal file with the database.


  • Server and database compatible version of swDatabaseManager.exe tool
  • If running against an sqlite database, the SystemWeaver server must be stopped, i.e., you must have sole access to the database
  • The database you are syncing the journal file with has journaling activated, and the .swjournal file matches, i.e., is associated with, the database

Note: The swDatabaseManager application is not for general distribution and should only be used by an authorized system administrator. 

Checking File/DB Match

  1. As noted in the prerequisites, the SystemWeaver server application should be stopped if running a sqlite database. 
  2. Open the swDatabaseManager.
  3. Select the database Type and Select database (e.g., you will be selecting the back-up database).
  4. On the Database tab, click the Display Info button to confirm that tool version is compatible with the database version. 
  5. On the Mirroring tab, click Check against dbto confirm that the journal file belongs to the selected database, i.e., their GUIDs match. The log will display that the journal is ahead of the database and will provide the last transaction id in the journal.


    In this example, the last id in the journal is 17.

Removing Extra Entries

  1. Next, click Remove extra entries to delete the extra entries from the journal file. This will put the database and journal file in sync with each other.


    The last transaction id in the database is 7. So, the journal file is 10 transactions ahead of the database (17-7=10). Therefore, the last 10 journal entries are removed.

Create New Cache File(s)

Once you have removed the extra transactions from the journal file, a new cache file will need to be generated for each mirror server. See How to Create a Cache File for Mirror Server.

What's Next?

You are now ready to restart the SystemWeaver main server against the database and then restart the mirror server.