The embedded database used by TapeTrack uses transactional protection. This means that as updates are applied to the underlying database, they are first written to a log file.
In the unlikely event that the TapeTrack Service abnormally terminates resulting in an inconsistent database, the database log files will be used to repair the database.
By default, TapeTrack is configured to expect that the High Availability option will be enabled. As a result, the database subsystem will retain all log files until at least one replicant is active.
If you do not expect to deploy the TapeTrack High Availability option, you must run the TapeTrack Service with the -X option, which will disable the replication subsystem.
Once you have either enabled at least one High Availability replicant or disabled the replication sub-system, you can remove redundant log files by either:
1. Specifying the set_flags DB_LOG_AUTOREMOVE option in your DB_CONFIG file.
2. Running the BerkeleyDB db_archive command.