Differences

This shows you the differences between two versions of the page.

--- server:database_logs [2017/06/06 17:53] – Gerard Nicol
+++ server:database_logs [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 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 Berkeley database subsystem will retain all log files until at least one replicant is active.
+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 sub-system (this is described in TMSS10Server).
+If you do not expect to deploy the TapeTrack High Availability option, you must [[technote:disable_replication|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:
-Specifying the set_flags ''DB_LOG_AUTOREMOVE'' option in your DB_CONFIG file.
+. Specifying the set_flags ''DB_LOG_AUTOREMOVE'' option in your [[server:db_config|DB_CONFIG file]].
+. Running the BerkeleyDB db_archive command.
+<- server:upgrading|Upgrading  ^ server:basic|Basic Administration ^ ->