LARGE single-system Cyrus installs?

[David Carter]

On Sun, 11 Nov 2007, Bron Gondwana wrote:

>> 250,000 mailboxes, 1,000 concurrent users, 60 million emails, 500k 
>> deliveries/day.  For us, backups are the worst thing, followed by 
>> reiserfs's use of BLK, followed by the need to use a ton of disks to 
>> keep up with the i/o.
>
> For us backups are hardly a blip on the radar :)  The joy of writing 
> your own custom backup system that knows more about Cyrus internals than 
> just about anything else.  It starts with some stat calls, and if any of 
> the cyrus.header, cyrus.index or cyrus.expunge files have changed then 
> it will lock them all then stream them all to the backup server.

Cyrus is pretty ideal for fast incremental updates to a backup system: 
hence replication. You shouldn't need to lock anything with delayed 
expunge, delayed delete and fast rename in place.

-- 
David Carter                             Email: David.Carter at ucs.cam.ac.uk
University Computing Service,            Phone: (01223) 334502
New Museums Site, Pembroke Street,       Fax:   (01223) 334679
Cambridge UK. CB2 3QH.