Kerio Connect on VMware [message #135553] |
Thu, 25 May 2017 02:40  |
zebby
Messages: 154 Registered: March 2009
|
|
|
|
Hello fellow admins,
We currently use Kerio connect on a physical Windows server and are looking to move this to a virtual.
Plan being that we'd take a machine and only run KC under VMware so negating the need for a Windows licence and hopefully hardening the security of the box plus gaining an advantage of rapid rebuild in the event of a disaster.
Does anyone have any thoughts, advice or best practice on using KC in a VM environment? For example virtual disks for everything or passthrough to physical? Any disadvantages to KC on VM at all? etc... etc...
Any input greatly received!
|
|
|
Re: Kerio Connect on VMware [message #135600 is a reply to message #135553] |
Tue, 30 May 2017 21:45  |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
We migrated from a Windows VM to a Linux (debian) VM. Important points:
- Linux seems to do disk I/O better, though our Windows VM was server 2K8, and may have had issues. I can't speak to direct to disk, because we're an HA environment with a SAN. We did test iSCSI vs NFS, and didn't see any significant difference either way.
- Use the documented "changing your OS" KB article, unless you have a very large existing data store, in which case you may have to use the same method we did, which involved Samba and robocopy.
- IMAPSYNC can mean practically zero downtime, but it also means not moving calendars & contacts, which makes it a non starter for most. I'd hoped by now Kerio would have cooked up something similar for just such a migration.
|
|
|