Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Optimizing disk utilization on a 3.2TB store
  •  
Hartz

Messages: 10
Karma: 0
Send a private message to this user
Hi all,

Looking for suggestions on optimizing storage for our Kerio Connect server.

Domains: 24
Users: 412
Mailbox Store: 3.2TB
Scenario: every user must keep every message back until the dawn of time, just in case.

We are about to migrate to a new server with additional storage on a Dell Compellent SAN. CentOS with ZFS pool for mail store is what I am investigating (we already run CentOS).

I really want to try deduplication but ZFS dedupe seems out of reach. 961 million 4k blocks for our existing 3.2TB store would require 307GB of memory to store the dedupe tables (providing my calcs are correct). My test of a single 200GB domain produced a dedupe ratio of 1.2 (shy of the 2.0 recommended for dedupe) so it seems to not be worth it either way; I thought this dedupe ratio seemed low though.

ZFS compression seems like a instant yes with improved disk I/O performance and only a hit to CPU load which is acceptable in our scenario.

Is there anything I am missing? Any alternate solutions? Some built in dedupe would be amazing.


Regards,
H.

[Updated on: Tue, 19 September 2017 03:27]

  •  
Bud Durland

Messages: 402
Karma: 45
Send a private message to this user
I'm not 100% certain, but from what I've seen of how Kerio stores messages on the server, I'm not sure a de-dupe application would be all that effective anyway. During a recent "all is well" GFI road map webinar, they said that a new message store database is coming in early 2018 (?), that will yield radically higher performance for searches and such. Maybe they will actually use a real dbms rather than flat text files.

How do you plan to migrate the message store? We used rsync and a creative script for a similar sized store to minimize user downtime.
  •  
Hartz

Messages: 10
Karma: 0
Send a private message to this user
Hi Bud,

I plan to rsync over n days and then have a final sync overnight for cutover. We already use rsync for backups rather than the built in backup process as it's quicker and just as effective.

Interesting news about the dbms in the roadmap. Definitely won't be rolling that update out on day 1.
  •  
Bud Durland

Messages: 402
Karma: 45
Send a private message to this user
Just to be clear, GFI did NOT specifically say there was a dbms based message store in the future, just that there would be a new datastore mechanism that would provide radically improved performance. I just don't see how that will happen without some type of dbms.
Previous Topic: Links to web sites not working consistently
Next Topic: GFI support
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Wed Nov 22 21:32:36 CET 2017

Total time taken to generate the page: 0.00370 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.