New Kolab install in a VM, practical partitioning & sizing recommendations?

Daniel Helgenberger daniel.helgenberger at m-box.de
Mon May 18 19:45:18 CEST 2015



On 18.05.2015 18:42, gornle at fastmail.com.au wrote:
> Well I'm "Batting 0" on this one :-/  Still can't find / figure out "best practices" or recommendations.
Hello,

I had a hard time also. But rest assured, the system requiremts are 
quite minimal compared to Exchange ;)

I run a small / medium instance with 50 accounts on a 2GB/2vCores VM. I 
think it might also run with only 1GB. I think this setup could well 
handle 10x this much.

There is at least a partitioning scheme; though it might be a little bit 
to 'physical' for a VM. [1] and some on storage tiering; though I found 
this does not work [3]

Keep in mind, your Data directory, so the largest and fasted storage, 
should be assigned to /var/spool/imap.

I think the dev distro of Kolab is EL, my VM runs El7 (centos 7.1) - no 
problems (except for the occasional imapd segfaults..., this seems to be 
platform unrelated) [2].

HTH,
Daniel

[1] 
https://docs.kolab.org/installation-guide/preparing-the-system.html#partitioning
[2] https://issues.kolab.org/show_bug.cgi?id=4979
[3] 
https://docs.kolab.org/administrator-guide/configuring-the-kolab-server.html#storage-tiering-of-the-imap-spool
>
> Is there a more appropriate place to ask Kolab questions like this?  Nothing here so far, nothing at #irc.
>
> More likely to get at a reply at ServerFault?
>
> I'll post where it's best to -- just like to avoid posting this a g'zillion times just to find the right place.
>
> Thanks!
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
>


More information about the users mailing list