[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: BDB Backend: How to force transaction log rotation for log archival based on db_archive
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: RE: BDB Backend: How to force transaction log rotation for log archival based on db_archive
- From: "Reiterer, Horst" <horst.reiterer@fabasoft.com>
- Date: Wed, 25 Jan 2017 18:29:42 +0000
- Accept-language: en-US, de-AT
- Content-language: en-US
- Thread-index: AdJ2hZfvVXZXkLSZQj+LD9aBDRcDzQAsprMw
- Thread-topic: BDB Backend: How to force transaction log rotation for log archival based on db_archive
Hi,
> Is there a way to force a transaction log rotation to make sure that even changes that do not cause
> a new transaction log to be created will get archived at regular intervals?
It can be done but the scenario definitely requires code to do so. The internal function __log_newfile can be used to switch to a new log file. After a checkpoint, the old log file will become unused and eligible for archiving.
Cheers,
Horst