use of glusterfs
I know the attachments are stored in /var/lib/kopano/attachments/ but where is the mail store? Is it in MySQL?
I’m thinking of running the /var/lib/mysql/ and /var/lib/kopano/ dirs (and maybe more) on a 3-node glusterfs. What could be the downside of such a construction?
but where is the mail store? Is it in MySQL?
What could be the downside of such a construction?
as long as you get enough iops out if this it should work.
Ok, IMHO Kopano’s big disadvantage is to store mail in a database. It’s a pity that Dovecot cannot be used as mailstore using maildir format.
I think the question is not if the database gets corrupted, but when. There are too many possible causes to corrupt a database (“Murphy was an optimist!”). I can run mysqldump of course (I’ve seen a kopano script somewhere for that IIRC) but what other measures can be taken to prevent the db from getting corrupted?
E.g.: Is it possible to use different databases for different organisations to limit possible damage? Should I use drbd instead of glusterfs?
Any thoughts on this matter?
I think the question is not if the database gets corrupted, but when.
the same can be said for a hard disk, a filesystem, a glusterfs cluster, a drbd partition.
We actually need to have the database to store everything in mapi format, this would not be as easy and performant when doing it directly in files (at least that is what I’m getting told all the time).
Mysql database corruption is not really a regular topic at our helpdesk. If you have destroyed your mysql database, then you have made a bunch of other mistakes beforehand (for example not monitoring your free disk space).
Is it possible to use different databases for different organisations
One kopano-server process always needs access to one mysql database. with our multiserver setup (requires ldap) you can have one setup consisting of multiple kopano-server processes.
Ok thnx Felix for pointing this out!
jengelh last edited by
The idea to store mails on disk is indeed compelling (especially the larger a message becomes). I have not formulated an idea yet as to what to do with the folder metadata, such as the hierarchy (defines which messages appears in what folder). Any glorious visions?