On Fri, Feb 10, 2012 at 12:00:29PM -0800, Philip Guenther wrote:
The optimized procedure that I worked out with Sleepycat's help (for a
completely different program, but using the transaction data store) was
this:
I'm exploring implementing these steps, but I'm running into some
confusion.
On Friday, 10 February 2012 01:04:09 Hallvard B Furuseth wrote:
Getting back to how to speed up restore:
If you do move to slapcat/slapadd, note that tuning slapd as described
in the Guide speeds up slapadd a lot, if you have not already done
that. So does the -q flag to slapadd.
--On Friday, February 10, 2012 5:05 PM +0200 Buchan Milne
bgmi...@staff.telkomsa.net wrote:
If you checkpoint, and you backup all the database files (including
transaction log files) in the correct order, you should not need to
db_recover (as database recovery can occur at a later time, if it
On Fri, Feb 10, 2012 at 09:35:12AM +0200, Buchan Milne wrote:
On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
On Thursday, 9 February 2012 21:00:36 Brian Reichert wrote:
FWIW: these scripts call out a bunch of reference URLs, that Oracle
has now broken:
On Fri, 10 Feb 2012, Buchan Milne wrote:
On Friday, 10 February 2012 01:48:45 Quanah Gibson-Mount wrote:
...
I thought I was very clear on that in my last email. It is not
sufficient. You need to stop slapd and run *db_recover*, which is more
exhaustive than db_checkpoint, if you want to
On Fri, Feb 10, 2012 at 12:00:29PM -0800, Philip Guenther wrote:
** Note that the ordering of this is almost completely inflexible.
** In particular:
** (0) must preceed (5)
** (1) must preceed (2) and (3)
** (2) and (3) must preceed (4)
**
On Fri, 10 Feb 2012, Brian Reichert wrote:
On Fri, Feb 10, 2012 at 12:00:29PM -0800, Philip Guenther wrote:
** Note that the ordering of this is almost completely inflexible.
** In particular:
** (0) must preceed (5)
** (1) must preceed (2) and (3)
**
--On Friday, February 10, 2012 3:32 PM -0500 Brian Reichert
reich...@numachi.com wrote:
Is management of a HDB backend's directory any easier?
back-hdb and back-bdb both use BDB as their data store. There is no
difference in how to handle backups between them.
--Quanah
--
Quanah
On Fri, Feb 10, 2012 at 03:02:51PM -0800, Quanah Gibson-Mount wrote:
back-hdb and back-bdb both use BDB as their data store. There is no
difference in how to handle backups between them.
OK, thanks for the clarification...
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
My implementation is shipped in my openldap packages (with symlinks in cron.*
enabled for daily backups by default), you can find the scripts here:
http://svnweb.mageia.org/packages/cauldron/openldap/current/SOURCES/ldap-hot-
On Tue, Feb 07, 2012 at 04:53:52PM -0500, Brian Reichert wrote:
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
Let me try asking a slightly different question.
This page says:
On 7/2/2012 11:53 μμ, Brian Reichert wrote:
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
We are using CentOS 5.7 too. Upgrade from 2.3.43 as has been suggested
already; it caused us
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
qua...@zimbra.com wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes incremental
backup by copying first the
--On Thursday, February 09, 2012 11:12 PM +0100 Hallvard B Furuseth
h.b.furus...@usit.uio.no wrote:
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
qua...@zimbra.com wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own
Hallvard B Furuseth wrote:
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
qua...@zimbra.com wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes
On Thu, 09 Feb 2012 14:36:20 -0800, Howard Chu h...@symas.com wrote:
Hallvard B Furuseth wrote:
The only officially supported backup method with OpenLDAP is
slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes
incremental
backup by
On Thu, Feb 09, 2012 at 02:36:20PM -0800, Howard Chu wrote:
Hallvard B Furuseth wrote:
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
qua...@zimbra.com wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
I wrote:
On Thu, 09 Feb 2012 14:36:20 -0800, Howard Chu h...@symas.com wrote:
Chapter 19 is obviously a work-in-progress, transferred over from
the
FAQ-o-Matic.
Presumably because backup has previously only been described in
the FAQ-o-Matic. But I'm pretty sure this has been the documented
--On Thursday, February 09, 2012 4:35 PM -0500 Brian Reichert
reich...@numachi.com wrote:
I do know that using the db_* utilities are only applicable to the
BDB backend. As far as I know, it's the most mature of the backends
to use with 2.3.43. (If I'm wrong in that, do let me know.)
2.3 is
On Thu, Feb 09, 2012 at 03:09:41PM -0800, Quanah Gibson-Mount wrote:
2.3 is not a supported release series. I would strongly advise upgrading
to a supported release.
Having tracked this project for years, I'm well aware of that stance,
but I'm trapped in a world where I'm stuck with what the
--On Thursday, February 09, 2012 5:17 PM -0500 Brian Reichert
reich...@numachi.com wrote:
What we're doing currently is:
- stopping slapd
- using db_checkpoint and db_archive to manage the BDB logs
- copy away the directory
- restart slapd
I'm trying to estabish if read-only mode is close
--On Thursday, February 09, 2012 5:30 PM -0500 Brian Reichert
reich...@numachi.com wrote:
I'm sorry; I thought you were focussing on my processing of the
directory's contents (which do need review, thanks), rather than
how I prepared slapd.
Ok. Now I now, read-only mode via the config
On Thursday, 9 February 2012 21:00:36 Brian Reichert wrote:
On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
My implementation is shipped in my openldap packages (with symlinks in
cron.* enabled for daily backups by default), you can find the scripts
here:
On Tuesday, 7 February 2012 23:53:52 Brian Reichert wrote:
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
The thread overall suggests the tried-and-true tactic of using
slapcat to extract
On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
On Tuesday, 7 February 2012 23:53:52 Brian Reichert wrote:
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
[snip]
What
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
The thread overall suggests the tried-and-true tactic of using
slapcat to extract and LDIF file, to be imported later. But, our
application's DB
26 matches
Mail list logo
