|Acrolinx Server||4.3, 4.4, 4.5, 4.6, 4.7, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 2018.10|
About the Acrolinx License Database
The Acrolinx server stores all information about licensed users in the Acrolinx license database. After you connect to the server for the first time, the server creates the license database.
The license database is created and stored at the following location:
The H2 license database replaces the license, user, and roles databases used in Acrolinx Server version 3.1 and lower.
The Acrolinx server regularly creates backups of the database in the following directory:
Add these database backups to your daily backup. Do not add the active database (the acrolinx.aldb.h2.db file) to the backup. Accessing an active database might cause errors.
Upgrades from earlier server versions
In Acrolinx Server versions 3.1 and lower, the license, user, and roles database were stored in a different format ( <NAME>.ald/.aud/.ard ) in the configuration directory. To upgrade to a later version from Server versions 3.1 and lower, you first need to upgrade to Acrolinx Server version 3.2, to make sure the existing databases are converted and merged into the new license database. You can then upgrade to a more recent Acrolinx version. The legacy database files are moved to the following directory:
Restoring License Database Backups
The Acrolinx server creates backups of the license database in the following directory:
The backups are created on an hourly basis. The file names contain a one-letter identifier, followed by an epoch timestamp. The identifier helps you to distinguish between hourly (H), daily (D), weekly (W) and monthly (M) backups. If you encounter an issue with the license database, you can use the backups to restore the database to a working state.
To restore a database backup, follow these steps:
- Stop the core server.
Unpack the relevant backup archive into the following directory:
- Restart the core server.
Use the Dashboard to verify that the backup was correctly restored.
For example, check that all users are present and that the role assignments are correct.