[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Transaction logging and OpenLDAP

On Fri, Aug 11, 2006 at 01:32:31PM -0400, matthew sporleder wrote:
> On 8/11/06, Tech Guy <techguymenlo@yahoo.com> wrote:
> >Hi,
> >
> >I understand that there have been several discussions
> >in the past about transaction logging on OpenLDAP. I

> I thought I remembered reading about a DB_CONFIG variable that would,
> essentially, turn of transactions for bdb (thus eliminating the logs).
> However, I don't think there's a good reason to do so.  My testing
> has shown that ldbm (the non-transactional bdb) is simply slower.  The
> I/O from these logs files is minimal, and they don't even take up much
> space with autoremove turned on.
> The DB_LOG_AUTOREMOVE makes the db_archive redundant, by the way.
> I don't think forcing the checkpoint is necessary, either.  Especially
> if you don't want to keep the log files around, and only doing one/day
> doesn't make a lot of sense unless it's followed by a few other
> scripts for backups.  Why not run them every hour?  Or just set the
> set_lg_max in DB_CONFIG to control the size of the transaction logs,
> and autoremove will take care of the ones that aren't needed for
> running.  10MB of write activity for an hour isn't exactly taxing on
> any modern system.

where is the docu on the autoremove ?

> I'll note, however, that getting rid of these logs eliminates one
> possible avenue of recovery.  All backups must now be taken using
> ldapsearch (for live backups) or with slapcat (for downed backups).
> What problem are you actually trying to solve?

Attachment: signature.asc
Description: Digital signature