I'm trying to create backup and restore scripts using LDAP command line tools. Creating a suitable backup and loading it are no problem. However, if I attempt to:
# ldapdelete -ZZ -r o=xxx,dc=yyyy,dc=zzz
It appears to work fine on the master replica where the command was run, but the other (MMR) master still maintains the entire DIT fragment. It doesn't ever seem to delete any of the entries.
Is there anything unique about the (-r) recursive ldapdelete? Is this behavior unique to "refreshOnly"? Should I use "refreshAndPersist"? Or do I need to implement a session log?
Thanks for any help or advice,
--On Tuesday, April 12, 2016 4:49 PM -0400 Frank Crow fjcrow2008@gmail.com wrote:
I'm trying to create backup and restore scripts using LDAP command line tools. Creating a suitable backup and loading it are no problem. However, if I attempt to:
Generally one does backup and restore using slapcat & slapadd. What are you trying to accomplish?
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
Frank Crow wrote:
I'm trying to create backup and restore scripts using LDAP command line tools.
For various reasons backup and restore should be done with command-line tools slapcat and slapadd which operate directly on the database files.
And yes, with recent backend modules like back-mdb and back-hdb you can do hot backup while slapd is running.
Of course, before a restore you have to stop slapd and remove the DB files. After using slapadd you should check whether ownership/permissions are still correct.
Ciao, Michael.
openldap-technical@openldap.org
-
Frank Crow -
Michael Ströder -
Quanah Gibson-Mount