Replication verification
Hi I have running two node back to back replication with 2.3.11 . The replication is running in both directions and with my small checks i didn't found any problem, the replication is runnig great. Now is the second server used only as replica of first server (hot-standby) and i'm searching for best practice , how to verify the replication, in best case continuously. I searchig for a posibility to use both server's in production as master-master. There are tools like nake_md5 and make_sha1, but the manpages document only howto config them, but not how to realy use them for replication check. Are there some scripts or methods, how to use them. Or are there other scenario how to efficiently verify replicated imap spool, quotas, annotations, acl's etc. ?? Kleo -- _ | You have moved the mouse. # | Windows must be restarted for the changes to take effect. # | OK # ##/ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Vladimir `KLEO' Klejch Kleo'at'netbox.cz ... ... ... ... Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication verification
On Fri, 27 Jun 2008, Vladimir Klejch wrote: I searchig for a posibility to use both server's in production as master-master. Afraid that replication in Cyrus doesn't support full master-master, only master/slave. UIDs in IMAP make full master-master rather involved. It is possible to run a mix of master and replica mailstores on a single system. There are tools like nake_md5 and make_sha1, but the manpages document only howto config them, but not how to realy use them for replication check. I download the md5 files to a single location and run a 50 line Perl script to spot mismatches. You are welcome to a copy of that script. To make sure that the replica is up to date I run sync_client in an extra verbose mode (-v -v) and check for unexpected updates. Unfortunately that code didn't make it it into the vanilla Cyrus tree because of the reorganisation required to run sync_server from master using prot streams for communication. It wouldn't take a huge amount of effort to add -v -v into standard Cyrus. I believe that Fastmail have an external test suite which does spot checks on the master and replica versions of each account. This is the opposite approach, and makes sense if you have a convenient IMAP client library. -- David Carter Email: [EMAIL PROTECTED] University Computing Service,Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication verification
On Fri, 27 Jun 2008, David Carter wrote: On Fri, 27 Jun 2008, Vladimir Klejch wrote: I searchig for a posibility to use both server's in production as master-master. Afraid that replication in Cyrus doesn't support full master-master, only master/slave. UIDs in IMAP make full master-master rather involved. It is possible to run a mix of master and replica mailstores on a single system. It's not really full master-master. I configured both servers as master/slave in cross, with different sync_machineid ( for UID computation ) and guid_mode: sha1. I tested this scenario, and it's working great. Changes on one server are replicated to the other one, and this in both directions. There are tools like nake_md5 and make_sha1, but the manpages document only howto config them, but not how to realy use them for replication check. I download the md5 files to a single location and run a 50 line Perl script to spot mismatches. You are welcome to a copy of that script. Yeah ... cann you mail me a copy for inspiration ?? Thanks. To make sure that the replica is up to date I run sync_client in an extra verbose mode (-v -v) and check for unexpected updates. Unfortunately that code didn't make it it into the vanilla Cyrus tree because of the reorganisation required to run sync_server from master using prot streams for communication. It wouldn't take a huge amount of effort to add -v -v into standard Cyrus. it would by nice to have methods to check replication in the mainstream. :-)) I believe that Fastmail have an external test suite which does spot checks on the master and replica versions of each account. This is the opposite approach, and makes sense if you have a convenient IMAP client library. I think, that only spot check are good for quick replication test, but not for verification of replication status. -- _ | You have moved the mouse. # | Windows must be restarted for the changes to take effect. # | OK # ##/ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Vladimir `KLEO' Klejch Kleo'at'netbox.cz ... ... ... ... Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
