[Date Prev][Date Next]
Re: Copying trees from one consumer to another
I've done this a number of times - Dev on an 'in production' ldap infrastructure. I've managed to get the boxes out of sync a number of times.
1. Stop slapd.
2. Delete the contents of the db dir
3. Copy a db-config into it.
4. Startup slapd.
The full tree is replicated pretty quickly. Try it out, you'll see. It take less then half a minute to replicate a tree with approx 800 entries (very rough estimate) even on slaves in AZ and masters in WA.
Chris Jacobs, Systems Administrator
Apollo Group | Apollo Marketing | Aptimus
2001 6th Ave Ste 3200 | Seattle, WA 98121
phone: 206.441.9100 x1245 | mobile: 206.601.3256 | fax: 206.441.9661
----- Original Message -----
From: openldap-technical-bounces+chris.jacobs=apollogrp.edu@OpenLDAP.org <openldap-technical-bounces+chris.jacobs=apollogrp.edu@OpenLDAP.org>
To: email@example.com <firstname.lastname@example.org>
Sent: Mon Jun 21 19:24:05 2010
Subject: Copying trees from one consumer to another
With slurpd, copying a tree from one slave to another was like this:
1. stop slapd on both slaves.
2. netcat the directory across from one slave to the other.
3. stop slurpd on master
4. edit slurpd.status to make the time and replication number match
by copying that for the source to that for the destination slave.
5. start everything back up.
My question with syncrepl is:
How do I copy the database for a tree from one consumer to another
consumer (of the same producer) so that the newly copied replica knows
where its replication should continue from?
Is the state for replication of the database stored in the contextCSN
of the suffix entry?
If so, does that mean that with syncrepl, the above operation is
reduced to the following three steps?
1. Stop slapd on both consumers.
2. Netcat the database from one to the other.
3. start both consumers.
Nick Urbanik http://nicku.org 808-71011 email@example.com
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
I disclaim, therefore I am.
This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.