Re: cyrus replication validation

2007-07-16 Thread Rob Mueller
Hi > If I understand this patch correctly, it doesn't solve the larger problem > that I'm interested in: is the data on my replica the same as the data on > my primary, or more to the point, are the two data sets converging? ... > But I'm really interested in something that can run out of

Re: cyrus replication validation

2007-07-16 Thread Wesley Craig
If I understand this patch correctly, it doesn't solve the larger problem that I'm interested in: is the data on my replica the same as the data on my primary, or more to the point, are the two data sets converging? This patch *would* allow me to more or less validate that the cyrus.* meta

Re: cyrus replication validation

2007-04-09 Thread John Capo
Quoting Dmitriy Kirhlarov ([EMAIL PROTECTED]): > On Fri, Apr 06, 2007 at 05:52:28PM -0400, John Capo wrote: > > > > On both servers: > > > find imap/ -type f | awk '!/(cache|index|header)/ {print}' | sort > > > > server1.lst > > > find imap/ -type f | awk '!/(cache|index|header)/ {print}' | sort

Re: cyrus replication validation

2007-04-08 Thread Dmitriy Kirhlarov
On Fri, Apr 06, 2007 at 05:52:28PM -0400, John Capo wrote: > > On both servers: > > find imap/ -type f | awk '!/(cache|index|header)/ {print}' | sort > > > server1.lst > > find imap/ -type f | awk '!/(cache|index|header)/ {print}' | sort > > > server2.lst > > > > and > > diff -u server1.lst ser

Re: cyrus replication validation

2007-04-06 Thread Rob Mueller
The provided Cyrus tool "make_md5" is for validating replication. It would, for instance, have found the recently discussed bug in sync_server that caused random files to be overwritten in the event that sync_server reused a stale staging file. It would probably be cool if there were doc

Re: cyrus replication validation

2007-04-06 Thread Wesley Craig
On 06 Apr 2007, at 17:52, John Capo wrote: Quick mailboxes.db check. ctl_mboxlist -d | md5 on server1 ctl_mboxlist -d | md5 on server2 Both hashes should be identical. Or diff the ctl_mboxlist -d outputs. The provided Cyrus tool "make_md5" is for validating replication. It would, for

Re: cyrus replication validation

2007-04-06 Thread John Capo
Quoting Dmitriy Kirhlarov ([EMAIL PROTECTED]): > On Thu, Apr 05, 2007 at 12:10:14PM -0400, Ilya Vishnyakov wrote: > > > Hello Cyrus Gurus! > > I was wondering if there is any specific way to check if the > > replication was done properly? I set up cyrus replication between two > > servers (documen

Re: cyrus replication validation

2007-04-06 Thread Ilya Vishnyakov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hmmm. it shows the equal sizes for both files. thank you. Dmitriy Kirhlarov wrote: > On Thu, Apr 05, 2007 at 12:10:14PM -0400, Ilya Vishnyakov wrote: > >> Hello Cyrus Gurus! >> I was wondering if there is any specific way to check if the >> replicati

Re: cyrus replication validation

2007-04-06 Thread Dmitriy Kirhlarov
On Thu, Apr 05, 2007 at 12:10:14PM -0400, Ilya Vishnyakov wrote: > Hello Cyrus Gurus! > I was wondering if there is any specific way to check if the > replication was done properly? I set up cyrus replication between two > servers (documentation I used: > http://cyrusimap.web.cmu.edu/imapd/install

Re: cyrus replication validation

2007-04-06 Thread Rudy Gevaert
Ilya Vishnyakov wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Cyrus Gurus! I was wondering if there is any specific way to check if the replication was done properly? I set up cyrus replication between two servers (documentation I used: http://cyrusimap.web.cmu.edu/imapd/install-r

cyrus replication validation

2007-04-05 Thread Ilya Vishnyakov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Cyrus Gurus! I was wondering if there is any specific way to check if the replication was done properly? I set up cyrus replication between two servers (documentation I used: http://cyrusimap.web.cmu.edu/imapd/install-replication.html). However,