Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » KMS in an ESX Environment
  •  
tek_san

Messages: 110
Karma: 0
Send a private message to this user
We just migrated our KMS 6.6 into an ESX environment.
Storage is provided by a Netapp Fas 2020 iSCSI Lun, with the size of 250GB.
We first thought about providing the drive in which the Kerio Mail Store resides in a vmdk and hook it into the ESX via NFS.

But as we don't have a Netapp Flexclone license restoring the mail store drive would be very time consuming.
Creating an iScsi clone can be done without extra licenses and so a restore of the KMS mail store is a matter of minutes.

The actual mail storage consumes 150 GB, with an average of 170 Users online, but only 10 of them are KOC (outlook connectors).

The ESX Servers are licensed to provide the HA (High Availability) feature, which fulfills our needs in security. We were one a tight budget, so we could not afford the ESX Enterprise version, that contains Vmotion.

So far, the experience is very good. Performance is no issue at all, as the average iSCSI performance is about 1 - 2 MB/sec.
Perfmon tells us there is no queue at all on the iScsi provided drive.
Performance remains the same as running the KMS on a physical Mailserver. We had a HP 380 G5 with a built in 0+1 RAID before.

The ESX Servers, we have two for the HA feature, are HP 380 G5 with 32 GB of RAM and 2 Quad Core Procs with 3 Ghz = 24 Ghz Proc capability.
The ESX runs about 15 virtual machines, including AD Master and NospamProxy Spam Filter.
The actual usage of RAM is about 10 - 12 GB and the processors consume about 12 - 14 Ghz. Disk or Network IO is low, very low...
The Servers have 4 Ethernetports each, all Gigabit connected and two are for administration, the other two for workload.
Of course this setup is a bit of overkill for KMS only, as the two netapps are about 45k Euro and the the ESX Servers, soft- and hardware are about 18k Euro.
But as we run a lot of machines on them, adding the KMS was just a logical step and as this setup provides enough redundancy.
I would say we have risen the level of operational availability of the KMS quit a bit.
Hope this helps you a bit in evaluating the KMS in a virtual environment.
regards

Oliver

[Updated on: Tue, 28 April 2009 14:40]


KC 7.3.1, Win2003 in vsphere 4.1, store drive attached via iSCSI, OS drive attached via NFS.
220+ IMAP Accounts: 210 OSX Mail /Entourage Clients, 10 Outlook 2003 KOC Clients - iPhones, Nokia E66, HTC 4350
Archive:EMA Appliance, SpamFilter: Nospamproxy
Previous Topic: KMS doesn't grant login to anyone
Next Topic: possible mini-bug in 6.7.0 RC1 - domain signature not in webmail
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: Fri Nov 24 21:07:22 CET 2017

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