--On Thursday, October 25, 2007 9:59 PM -0400 Francis Swasey Frank.Swasey@uvm.edu wrote:
You don't? Does your accesslog DB keep it's contextCSN updated while the server runs or does it only update the contextCSN when you start slapd?
It updates the context CSN every time a modification is made. The syncprov checkpoint has nothing to do with that behavior.
Fresh DB with no changes:
[zimbra@freelancer libexec]$ ldapsearch -LLL -x -D "uid=zimbra,cn=admins,cn=zimbra" -h freelancer -W -b "" -s base contextCSN Enter LDAP Password: dn: contextCSN: 20071027180930Z#000001#00#000000
[zimbra@freelancer libexec]$ ldapsearch -LLL -x -D "uid=zimbra,cn=admins,cn=zimbra" -h freelancer -W -b "cn=accesslog" -s base contextCSN Enter LDAP Password: dn: cn=accesslog contextCSN: 20071027180930Z#000000#00#000000
As you can see, the context CSN's match.
Now, I add a user.
[zimbra@freelancer libexec]$ ldapsearch -LLL -x -D "uid=zimbra,cn=admins,cn=zimbra" -h freelancer -W -b "" -s base contextCSN Enter LDAP Password: dn: contextCSN: 20071027181210Z#000000#00#000000
[zimbra@freelancer libexec]$ ldapsearch -LLL -x -D "uid=zimbra,cn=admins,cn=zimbra" -h freelancer -W -b "cn=accesslog" -s base contextCSN Enter LDAP Password: dn: cn=accesslog contextCSN: 20071027181210Z#000000#00#000000
As you can see, the contextCSN's still match.
And, here's the contextCSN on the replica:
[zimbra@tribes ~]$ ldapsearch -LLL -x -D "uid=zimbra,cn=admins,cn=zimbra" -h freelancer -W -b "" -s base contextCSN Enter LDAP Password: dn: contextCSN: 20071027181210Z#000000#00#000000
Everything's happy.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration