Rich Graves wrote:
> Clustered filesystems don't make any sense for Cyrus, since the
> application itself doesn't allow simultaneous read/write. Just use a
> normal journaling filesystem and fail over by mounting the FS on the
> backup server. Consider replication such as DRDB or proprietary SAN
>
Pascal Gienger wrote:
> There are techniques to handle these situations - for xfs (as an
> example) consider having *MUCH* RAM in your machine and always mount it
> with logbufs=8.
Is XFS so RAM intensive?
> I would NEVER suggest to mount the cyrus mail spool via NFS, locking is
> important and f
David S. Madole wrote:
> My limited experience is that you can simply copy both /var/spool/imap
> and /var/lib/imap to the new machine if you are trying to migrate
> everything.
>
> One way to do this to minimize downtime if you have a lot of data is to
> make a live copy while the old server is s
Hi everyone,
simple question: is there a fancy method to migrate all the Cyrus IMAP
mailboxes and databases from a box to a new one?
I'm planning this because the current box is running out of resources
(very bad).
The old box runs cyrus-imapd-2.2.6-5 and db4-4.1.25-8.1 while new one
has cyrus-i
