Earlier, I wrote:
>> What do I need to do in order for changes made on the replica
>> to get copied over to the master?
Bron Gondwana replied:
> Impossible. You don't do this. What you can do (the simple
> case of what we do) is set up two Cyrus instances on each
> machine, replicating to each
On Sat, Nov 10, 2007 at 07:09:53PM -0800, Rich Wales wrote:
> After about a week of having synchronization running perfectly in my
> 2.3.9 system, I finally got another bailout incident with sync_client
> on my master server.
>
> This happened just after I shut down my replica server (to move it t
On Sat, Nov 10, 2007 at 07:51:15PM -0800, Rich Wales wrote:
> I'm using replication on a 2.3.9 system.
>
> I know that if changes happen on the master system, they are propagated
> automatically to the replica system.
>
> But what happens if I make a change on the replica (e.g., by setting up
> a
On Sun, Nov 11, 2007 at 02:31:45PM +1100, Bron Gondwana wrote:
> * the one buggy skiplist I actually still have a copy of, the "logstart"
> value in the header is wrong, causing recovery to fail with only a few
> of the records still reachable because it hits another INORDER record
> rather t
Subject: Re: How many people to admin a Cyrus system?
> On Thu, 8 Nov 2007, Gary Mills wrote:
>
>> We have a moderate-sized Cyrus system for 30,000 students and 3000
>> employees. It's a critical service in the sense that thousands of
>> people depend on it. It has excellent performance, lots o
