>> While I understand it takes effort to maintain the replication plugin, this >> is especially problematic for small active/active high-availability >> deployments. > > To clarify: replication absolutely does not provide "active/active". > Replication was meant to copy data to a standby server, but you can't have > concurrent mailbox access. This is why directors existed.
I have to disagree, active/active with two distinct servers is a special case and two-way replication has been working reliably in production for years. Here's why: those two imap servers are separate instances with local storage, local quota and local pruning. There is no shared medium access like nfs that could lead to data corruption and hence no directors needed. Moreover the dsync manpage states "doveadm-sync - Dovecot's two-way mailbox synchronization utility". It's more like IMAP-clients copying mails from one server to another where the most current state wins. >> I guess there are lots of servers that use replication for just 50 or 100 >> mailboxes. Cloudstorage (like S3) would be overkill for these. >> >> Do you provide dovecot pro subscriptions for such small deployments? > > A 50-100 mailbox user server will run Dovecot CE just fine. Pro would be > overkill. > > All current Dovecot development assumes that storage is decoupled from the > system. Shared (as in network available) storage is what you need if you > want high availability, whether in Pro or CE. Thanks for clarification. So even if mdbox is still available and replication (backup) would work with dsync on the command line, there is no signaling layer to auto-trigger replication because storage is decoupled and this functionality is not needed anymore. Best regards, Gerald _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
