On Wed, Jan 30, 2013 at 04:19:17PM +0100, Meike Stone wrote:
Thanks for enlighten me. I've a separate backup server (read only
slave), where I can do this.
So I'll try to get money from the FC for more RAM to make the test in
a ramdisk ^^
You may not need to expand the physical RAM. Most
On Mon, Jan 28, 2013 at 12:15:19PM +0100, Meike Stone wrote:
I think, it would be a great thing to test the slapcat file (after
dumping it) instantly.
Testing backups is always wise...
So as reported in
http://www.openldap.org/lists/openldap-technical/201301/msg00254.html
I tried to do
Hello Andrew,
Dryrun won't be able to detect missing structural entries: that
requires a database. Even an internal list of DNs is not
enough, as the actual entries have to be available in order to
check things like schema and content rules.
To be a valid test you really have to import the
Meike Stone wrote:
2013/1/24 Hallvard Breien Furuseth h.b.furus...@usit.uio.no:
Meike Stone writes:
- What ist the origin for such orphaned nodes (In MMR, it happens and
I see a few glue records, but in my backup this one node is complete
missing...)?
Do you check the exit code from slapcat
- How can I prevent from such entires and how can I recognize them
without importing?
It's easiest just to let slapadd tell you.
So I understand, I make a dry-run (slapadd -u) to test the backup?
I tried this, but got no error, only if I make a real import, then
slapadd throws the error.
2013/1/24 Hallvard Breien Furuseth h.b.furus...@usit.uio.no:
Meike Stone writes:
- What ist the origin for such orphaned nodes (In MMR, it happens and
I see a few glue records, but in my backup this one node is complete
missing...)?
Do you check the exit code from slapcat before saving its
and if I try to add this missing node, then I get:
ldapadd -x -h localhost -w password -Dcn=admin,ou=root -f test.ldif
adding new entry ou=a,ou=b,ou=c,ou=root
ldap_add: Already exists (68)
Use slapadd to add the missing entry. For back-mdb you don't need to stop
slapd while running other
Meike Stone wrote:
Hello dear List,
I tried to import a slapcat backup from our production machine in a
test environment and got following message:
debld02:~ # time slapadd -w -q -f /etc/openldap/slapd.conf -l /backup.ldif
50f98421 mdb_monitor_db_open: monitoring disabled; configure monitor
Meike Stone writes:
- What ist the origin for such orphaned nodes (In MMR, it happens and
I see a few glue records, but in my backup this one node is complete
missing...)?
Do you check the exit code from slapcat before saving its output?
If slapcat (well, any program) fails, discard the output
