On Thursday 16 July 2009 @ 11:05, Nic Bernstein wrote:
> Brian,
> I certainly would be interested in seeing those. Please post them
> here, or to the Wiki.
>
> Best regards,
> -nic
Our email operations group manager put together a summary of our cyrus
implementation recently for a meeting
On Fri, 17 Jul 2009, David Mayo wrote:
>
> Andrew Morgan wrote:
>
>> On Thu, 16 Jul 2009, Gavin Gray wrote:
>>
>>> We are planning towards upgrading our existing murder. The murder has
>>> four front ends, three backends and separate mupdate and lmtp servers.
>>> We want to move from version 2.2.
Andrew Morgan wrote:
> On Thu, 16 Jul 2009, Gavin Gray wrote:
>
>> We are planning towards upgrading our existing murder. The murder has
>> four front ends, three backends and separate mupdate and lmtp servers.
>> We want to move from version 2.2.12 to 2.3.14 so that we can make use
>> of delaye
On Thu, 16 Jul 2009, Gavin Gray wrote:
> We are planning towards upgrading our existing murder. The murder has
> four front ends, three backends and separate mupdate and lmtp servers.
> We want to move from version 2.2.12 to 2.3.14 so that we can make use
> of delayed expunge an possible replicati
On Thursday 16 July 2009 @ 09:53, Rudy Gevaert wrote:
>
> I wonder if it is possible to run sync to two different servers.
>
> Anyone?
AFAIK, Not easily. We considered trying to do this when we moved from
tape backup to disk based backup. We decided on an out of band
process to replicate to o
On 07/16/2009 09:55 AM, Brian Awood wrote:
> On Thursday 16 July 2009 @ 05:21, Gavin Gray wrote:
>
> replication is significantly slower than xfer, but it shouldn't affect
> the speed of xfer. We wrote some scripts to prevent xfer from
> getting too far ahead of replication. Since our replic
On Thursday 16 July 2009 @ 05:21, Gavin Gray wrote:
> 2. We should end up then with our existing murder but with three
> backends running 2.3.14. We then plan to upgrade the other machines
> in the murder to 2.3.14 in the following order: frontends then lmtp
> and finally the mupdate server. Does
Hi,
Citeren Michael Menge :
> You need both rolling replication and one replication of all users.
> The rolling replication will only sync what has changed. So if a user
> recieves new mail, rolling replication will sync the mailbox, but not
> the sieve scripts or the subscribtion list. It does
Quoting Gavin Gray :
Assuming we do do the migration first, how would you suggest we
subsequently enable replication? Can we just start the sync_client
doing rolling replication, or should we do an initial replication of
all users by running sync_client manually with a list of users?
Hi,
Y
Gavin Gray wrote:
> Assuming we do do the migration first, how would you suggest we
> subsequently enable replication? Can we just start the sync_client doing
> rolling replication, or should we do an initial replication of all users
> by running sync_client manually with a list of users?
We e
Quoting Dave McMurtrie :
>> 3. As part of our preparation for this work we have been experimenting
>> with cyrus replication. The replication protocol seems pretty solid,
>> however we have some concerns about how to make use of it in our
>> upgrade. We are considering having a replicant machine
Gavin Gray wrote:
> We are planning towards upgrading our existing murder. The murder has
> four front ends, three backends and separate mupdate and lmtp servers.
> We want to move from version 2.2.12 to 2.3.14 so that we can make use
> of delayed expunge an possible replication.
>
> We have
12 matches
Mail list logo
