Replication documentation anywhere?

Karl Pielorz kpielorz_lst at tdx.co.uk
Fri May 24 04:41:17 EDT 2013


--On 24 May 2013 11:10 +1000 Bron Gondwana <brong at fastmail.fm> wrote:

> I'm afraid there isn't much :(  Feel free to ask questions about
> specific things you run in to, and we can use that as a basis to put
> together more detailed documentation.

Hi,

Thanks for your reply (which I've read through now!) - if we have an 
existing mailstore (with ~2-3 million emails) and we setup a replica is 
'sync_client' going to be able to bring the replica to the same state as 
the master? (given time, and not too many changes on the master?) - or are 
we better off using another method (such as FS snapshot -> replica).

Presumably the replication doesn't do anything for users (we use sasl for 
auth, i.e. saslpasswd2 to create the users) - if we intend to have users 
'hitting' the replica (when the master as failed) presumably we'd need to 
create those users / passwords on the replica as well?

In a nutshell - when we have the master / replica setup, if we 'switch' to 
having users hit the replica (because the master has failed) - it appears 
we can simply 'switch' the replication configs over, and then have what was 
the master 're-sync' with the new master?

I guess what I'm trying to figure out is if the replication / 'sync_client' 
is the 'magic' solution is appears to be - i.e. given enough bandwidth, 
time / 'grunt' & low enough volume of changes on the master - it'll drag an 
empty mailstore up to be an identical replica, or re-sync a once failed 
master to be a new replica.

Thanks again for your time,

-Karl


More information about the Cyrus-devel mailing list