Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 

Managing Archive Logs

You must not delete archive logs by using the file deletion command such as rm or del by yourself; the archive logs should be deleted by system configuration or the cubrid backupdb utility. In the following three cases, archive logs can be deleted.

  • In an HA environment, configure the value of force_remove_log_archives to no and specify the number in the value of log_max_archives (logs are deleted after replication applied).
  • In non-HA environment, configure the value of force_remove_log_archives to yes and specify the number in the value of log_max_archives.
  • Use cubrid backupdb -r; note that it should not be used in an HA environment.

If you want to delete logs as much as possible while operating a database, configure the value of log_max_archives to 0 or as small as possible and configure the value of force_remove_log_archives to yes. Note that in an HA environment, if the value of force_remove_log_archives is yes, archive logs that have not replicated in a slave node are deleted, which can cause replication errors. Therefore, it is recommended that you configure it to no. Although the value of force_remove_log_archives is set to no, files that are complete for replication can be deleted by HA management process.