[Date Prev][Date Next]
Re: (ITS#6365) Bad slapcat output when slapd running
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#6365) Bad slapcat output when slapd running
- From: firstname.lastname@example.org
- Date: Sat, 14 Nov 2009 07:43:55 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
Howard Chu wrote:
> email@example.com wrote:
>> Pierangelo Masarati wrote:
>>> You appear to be using back-hdb.
>>> My guess is that if this can fail, e.g. because entries are being
>>> sync'ed out of order, the DN does not get fixed. If this is the case (I
>>> couldn't inspect code deep enough to make sure), I'd expect that the DN
>>> get fixed anyway, though, because missing entries should exist as "glue"
>> yes. But if you plan to use slapcat as a backup mechanism, then it's
>> still a problem.
> Sounds like a low priority issue at best. Taking backups of a replica while it
> is initializing is pointless, just take a backup of the provider instead.
This is mirrormode.
There's no "provider" as such. However, there's one server which is used
for application access and to minimize disk load on that server, the
plan was to take most backups from the other.
I can't see any difference between what you call "initializing" and
normal running state, except that the difference between server-1 and
server-2 is (somewhat) larger. If I can't trust slapcat during this
phase, how can I trust slapcat for backups?