Eric, Egoitz
thank you very much, all your advices are very interesting.
Egoitz, replication and delayed expunged are previewed for the next
migration.
I'm not sure that cyrus2.3 implements delayed expunged.
Eric, here is a piece of fstab for mounting nfs:
Hi!,
I'm an experienced user too... more than 10 too :)
It's just an advice... I'd recommend using Cyrus replication as an HA
mech. We use an own made mech for restoring mailboxes... the snapshot
causes often mailboxes to need a reconstruction. Obviously if it has
worked for you perhaps
On 06/12/2018 11:17, Ismaël Tanguy wrote:
Hello,
thanks for your answer.
We have been using for more than 10 years Cyrus with NFS because of
the snapshot.
Snapshot give a way to restore mail or mailbox.
It has worked like a charm until the migration.
Now we're stuck on daily mailbox
Hello,
thanks for your answer.
We have been using for more than 10 years Cyrus with NFS because of the
snapshot.
Snapshot give a way to restore mail or mailbox.
It has worked like a charm until the migration.
Now we're stuck on daily mailbox corruption due to this storage.
We're looking,
Hi!
Mate nfs, is no tan appropiate storage for Cyrus. I’d recommend you using
machine local storage. Using that kind of config won’t success.
Cheers,
Egoitz,
> El 5 dic 2018, a las 12:13, Ismaël Tanguy
> escribió:
>
> Hello, this is a Cyrus 2.3.11 on Centos 5.
> About 5000 users for 10 To.
Hello, this is a Cyrus 2.3.11 on Centos 5.
About 5000 users for 10 To.
Mail storage has been moved from NetApp NFS to FluidsFS (aka Dell
Compellent NFS).
Since an update on FluidFS, Imap spool undergoes daily NFS timeouts
which leads to corrupt mailboxes.
Typically, this begins with lines
