From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/transapp_logfile.html | 108 +++++++++++++++--------- 1 file changed, 69 insertions(+), 39 deletions(-) (limited to 'docs/programmer_reference/transapp_logfile.html') diff --git a/docs/programmer_reference/transapp_logfile.html b/docs/programmer_reference/transapp_logfile.html index fd130e3f..f44aebaa 100644 --- a/docs/programmer_reference/transapp_logfile.html +++ b/docs/programmer_reference/transapp_logfile.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 11.  - Berkeley DB Transactional Data Store Applications - Chapter 11.  Berkeley DB Transactional Data Store Applications  Next
@@ -38,46 +36,77 @@
-

The fourth component of the infrastructure, log file removal, concerns -the ongoing disk consumption of the database log files. Depending on -the rate at which the application writes to the databases and the -available disk space, the number of log files may increase quickly -enough so that disk space will be a resource problem. For this reason, -you will periodically want to remove log files in order to conserve disk -space. This procedure is distinct from database and log file archival -for catastrophic recovery, and you cannot remove the current log files -simply because you have created a database snapshot or copied log files -to archival media.

-

Log files may be removed at any time, as long as:

+

+ The fourth component of the infrastructure, log file + removal, concerns the ongoing disk consumption of the database + log files. Depending on the rate at which the application + writes to the databases and the available disk space, the + number of log files may increase quickly enough so that disk + space will be a resource problem. For this reason, you will + periodically want to remove log files in order to conserve + disk space. This procedure is distinct from database and log + file archival for catastrophic recovery, and you cannot remove + the current log files simply because you have created a + database snapshot or copied log files to archival + media. +

+

+ Log files may be removed at any time, as long as: +

-

Additionally, when Replication Manager is running -the log file is older than the most out of date active site in the -replication group.

-

If you are preparing for catastrophic failure, you will want to copy -the log files to archival media before you remove them as described in -Database and log file archival.

-

If you are not preparing for catastrophic failure, any one of the -following methods can be used to remove log files:

+

+ Additionally, when Replication Manager is running the log + file is older than the most out of date active site in the + replication group. +

+

+ If you are preparing for catastrophic failure, you will want + to copy the log files to archival media before you remove them + as described in Database and log file + archival. +

+

+ If you are not preparing for catastrophic failure, any one + of the following methods can be used to remove log + files: +

    -
  1. Run the standalone db_archive utility with the -d -option, to remove any log files that are no longer needed at the time -the command is executed.
    2. -
  2. Call the DB_ENV->log_archive() method from the application, with the -DB_ARCH_REMOVE flag, to remove any log files that are no longer -needed at the time the call is made.
    3. -
  3. Call the DB_ENV->log_set_config() method from the application, with the -DB_LOG_AUTO_REMOVE flag, to remove any log files that are no -longer needed on an ongoing basis. With this configuration, Berkeley DB will -automatically remove log files, and the application will not have an -opportunity to copy the log files to backup media.
    4. +
  4. + Run the standalone db_archive utility with the -d option, to remove any log + files that are no longer needed at the time the command is + executed. +
    5. +
  5. + Call the DB_ENV->log_archive() method from the application, + with the DB_ARCH_REMOVE flag, to remove any log files + that are no longer needed at the time the call is + made. +
    6. +
  6. + Call the DB_ENV->log_set_config() method from the + application, with the DB_LOG_AUTO_REMOVE flag, to remove + any log files that are no longer needed on an ongoing + basis. With this configuration, Berkeley DB will + automatically remove log files, and the application will + not have an opportunity to copy the log files to backup + media. +
@@ -92,7 +121,8 @@ opportunity to copy the log files to backup media.  Next - Database and log file archival  + Database and log file + archival  Home -- cgit v1.2.1