[Date Prev][Date Next]
Re: new admin guide draft
>Just a short note without having used this new replication engine so far:
>With another LDAP server product it is sometimes faster to dump the whole
>database at once (in a special replica LDIF format), copy it to the replica
>system and load the database from LDIF than using the function "Initialize
>Consumer" which pushes the whole database via LDAP.
>Therefore I could imagine that it'd be nice to do a slapcat (replica mode)
>on provider, scp/ftp/whatever to replica system and slapadd on replica system.
What I have in mind is the combinations of three options in slapdadd.
slapadd -p : promote : if syncrepl%d entries are found (consumer->provider)
find maximum cookie value out of the syncreplCookie stored in them,
and create an ldapsync entry containing the maximum cookie value.
do not add the syncrepl%d entries in the provider replica.
else if ldapsync entry is found (provider->provider)
add it to the provider replica as is.
slapadd -r : demote : if ldapsync entry is found (provider->consumer)
create syncrepl%d entries having the contextCSN stored in the ldapsync entry.
else if syncrepl%d entries are found (consumer->consumer)
add them to the consumer replica as is.
-w : if -w option is used in addition to -p / -r,
slapadd will recalculate the contextCSN and syncreplCookie in the
ldapsync and syncrepl%d entries respectively,
based on the entryCSN of the entries.
(hard to find appropriate letters left available in the slaptool options...)
BTW, Kurt and I had a discussion on a new tool that promotes and demotes
replicas at the database level. Regardless a backup is obtained
at ldif or database level, the backup contains its sync status in the CSN form.
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
(phone) 914-945-3979 (fax) 914-945-4425 TL: 862-3979