diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/transapp_logfile.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/transapp_logfile.html')
| -rw-r--r-- | docs/programmer_reference/transapp_logfile.html | 108 |
1 files changed, 69 insertions, 39 deletions
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 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="transapp_archival.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Berkeley DB Transactional Data Store Applications - </th> + <th width="60%" align="center">Chapter 11. Berkeley DB Transactional Data Store Applications </th> <td width="20%" align="right"> <a accesskey="n" href="transapp_recovery.html">Next</a></td> </tr> </table> @@ -38,46 +36,77 @@ </div> </div> </div> - <p>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.</p> - <p>Log files may be removed at any time, as long as:</p> + <p> + 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. + </p> + <p> + Log files may be removed at any time, as long as: + </p> <div class="itemizedlist"> <ul type="disc"> - <li>the log file is not involved in an active transaction.</li> - <li>a checkpoint has been written subsequent to the log file's -creation.</li> - <li>the log file is not the only log file in the environment.</li> + <li> + the log file is not involved in an active + transaction. + </li> + <li> + a checkpoint has been written subsequent to the log + file's creation. + </li> + <li> + the log file is not the only log file in the + environment. + </li> </ul> </div> - <p>Additionally, when Replication Manager is running -the log file is older than the most out of date active site in the -replication group.</p> - <p>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 -<a class="xref" href="transapp_archival.html" title="Database and log file archival">Database and log file archival</a>.</p> - <p>If you are not preparing for catastrophic failure, any one of the -following methods can be used to remove log files:</p> + <p> + Additionally, when Replication Manager is running the log + file is older than the most out of date active site in the + replication group. + </p> + <p> + 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 <a class="xref" href="transapp_archival.html" title="Database and log file archival">Database and log file + archival</a>. + </p> + <p> + If you are not preparing for catastrophic failure, any one + of the following methods can be used to remove log + files: + </p> <div class="orderedlist"> <ol type="1"> - <li>Run the standalone <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility with the <span class="bold"><strong>-d</strong></span> -option, to remove any log files that are no longer needed at the time -the command is executed.</li> - <li>Call the <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a> method from the application, with the -<a href="../api_reference/C/logarchive.html#archive_DB_ARCH_REMOVE" class="olink">DB_ARCH_REMOVE</a> flag, to remove any log files that are no longer -needed at the time the call is made.</li> - <li>Call the <a href="../api_reference/C/envlog_set_config.html" class="olink">DB_ENV->log_set_config()</a> method from the application, with the -<a href="../api_reference/C/envlog_set_config.html#log_set_config_DB_LOG_AUTO_REMOVE" class="olink">DB_LOG_AUTO_REMOVE</a> 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.</li> + <li> + Run the standalone <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility with the <span class="bold"><strong>-d</strong></span> option, to remove any log + files that are no longer needed at the time the command is + executed. + </li> + <li> + Call the <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a> method from the application, + with the <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_REMOVE" class="olink">DB_ARCH_REMOVE</a> flag, to remove any log files + that are no longer needed at the time the call is + made. + </li> + <li> + Call the <a href="../api_reference/C/envlog_set_config.html" class="olink">DB_ENV->log_set_config()</a> method from the + application, with the <a href="../api_reference/C/envlog_set_config.html#log_set_config_DB_LOG_AUTO_REMOVE" class="olink">DB_LOG_AUTO_REMOVE</a> 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. + </li> </ol> </div> </div> @@ -92,7 +121,8 @@ opportunity to copy the log files to backup media.</li> <td width="40%" align="right"> <a accesskey="n" href="transapp_recovery.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Database and log file archival </td> + <td width="40%" align="left" valign="top">Database and log file + archival </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> |