TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


server:database_logs

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
server:database_logs [2017/06/06 17:54] Gerard Nicolserver:database_logs [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 7: Line 7:
 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. 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.+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: 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.+1. Specifying the set_flags ''DB_LOG_AUTOREMOVE'' option in your [[server:db_config|DB_CONFIG file]]. 
 + 
 +2. Running the BerkeleyDB db_archive command. 
 + 
 +<- server:upgrading|Upgrading  ^ server:basic|Basic Administration ^ -> 
  
server/database_logs.1496771643.txt.gz · Last modified: 2025/01/21 22:07 (external edit)