Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Migration - Kerio 8.2.4 from OS X to Kerio 9.0.2 on Windows Server (Need suggestions and your experiences)
  •  
vindiesel.dd

Messages: 6
Karma: 0
Send a private message to this user
Hi everyone,

first of all, sry for my bad grammar Smile

Currently we are running Kerio Connect 8.2.4 patch1(32bit) on Mac OS X 10.5.8 Server and we need to migrate in short-range to a newer Kerio Version and to a server with much more performance and availability.
Our Mailstore is about 450GB, stored on a single 7.2k Nearline S-ATA Disk. The destination server should become a virtualized Windows Server 2012 R2 with Kerio Connect 9.0.2(64bit).

I want to migrate the store via a third-party sync tool like rsync in following steps:
- Initial MailStore Sync
- Stop Kerio Mail Server
- Second sync of the MailStore and Config-files
- modify the datastore path in the config-files
- start up the new Kerio server and register again
(Because the complexity and that no mistakes are allowed, i will make a test-migration with trial key before)

In following KB you can read the prequesite, that the source and destination kerio connect server should be the same version.
kb.kerio.com/product/kerio-connect/server-configuration/expo rt-and-migration/transferring-an-installation-of-kerio-conne ct-to-another-server-or-operating-system-360.html

Unfortunately, i'm not able to update the Kerio Connect on OS X because there is no newer version supporting OS X 10.5 and there is no 8.2.4 version supporting Windows Server.
Beacuse the OS X 10.5 Server is mission critical, i dont want to risk a OS X Update and i don't really have a time-span to take offline this server for a longer time to update the OS X or something else.

I hope now, anybody from you guys can help me with suggestions or experiences migrating mailstore between different Kerio Connect Versions and give me some hints what to pay attention to, when migrating from OS X to Windows Server and 32Bit to 64Bit Kerio.

Thanks
  •  
Maerad

Messages: 147
Karma: 29
Send a private message to this user
Mhh...

http://download.kerio.com/archive/

Kerio Connect > Windows > Version 8.2.4

Install it on the Windows Server.

For the transfer I would suggest you get yourself an external HDD or local NAS and do a backup with kerio. Then restore to the Windows Server. That IS the fastest and safest way.

And please, PLEASE, get yourself a raid - at least a raid 1 with 2 HDD. Best would be a Raid 10 or 5 with 4x 15k SATA HDD. Those are quite cheap right now and WAY faster then any SATA. Not to mention the data protection a raid offers per se and the lesser error margin.

One HDD for a mission critical server is ... wow. And a Sata too. If that HDD fails, everything of the day is lost and it needs some time to restore 450 GB. On a raid if the HDD fails, you can just remove the HDD for a new one. Or won't it matter, that the mail server will be down for like 6-8 hours? (Find the error, get new HDD, build in, get ready, copy data etc.)
  •  
vindiesel.dd

Messages: 6
Karma: 0
Send a private message to this user
Hi Maerad,

thank you for your response. Unfortunately i'm only able to find the version 8.3.4 patch1 for Windows. I will meet your desires Smile The virtualized Windows Server will be operating on a vmware vsphere hypervisor with raid5 sas disks and hot spare. Fortunately, the costs for the disks doesn't matter. I'm aware of the huge risk with the single disk. But as so much things in IT, it grown up and the time is short. ^^ I will think about your suggestions with the staging disk to transfer the data, maybe its a good idea.
  •  
Maerad

Messages: 147
Karma: 29
Send a private message to this user
vindiesel.dd wrote on Fri, 11 March 2016 14:25
Hi Maerad,

thank you for your response. Unfortunately i'm only able to find the version 8.3.4 patch1 for Windows. I will meet your desires Smile The virtualized Windows Server will be operating on a vmware vsphere hypervisor with raid5 sas disks and hot spare. Fortunately, the costs for the disks doesn't matter. I'm aware of the huge risk with the single disk. But as so much things in IT, it grown up and the time is short. ^^ I will think about your suggestions with the staging disk to transfer the data, maybe its a good idea.


Hehe, that I know with the growing shit and someone has to correct it, best yesterday.

But for the version ... dude..

http://download.kerio.com/archive/download.php > Select: Kerio Connect Version: 8.3.4 Patch 1

Then to "show files" and dl the windows x64 file. If you use Active Directory, you should also DL the AD Extensions.

http://cdn.kerio.com/dwn/connect/connect-8.3.4-3377/kerio-co nnect-8.3.4-3377-p1-win64.exe
http://cdn.kerio.com/dwn/connect/connect-8.3.4-3377/kerio-co nnect-kade-8.3.4-3377-p1-win64.exe
  •  
Bud Durland

Messages: 356
Karma: 38
Send a private message to this user
As someone who has done this kind of thing several times, Please let me make a couple suggestions:

If possible, use Linux for the new mail host. I realize that this is dependent on your expertise and comfort level with Linux vs. Windows, but the performance is much better. I prefer creating the Linux VM, then installing Kerio COnnect, rather than installing the Connect appliance. I'm not implying that WIndows Server won't work, just that IMHO, linux does it better.

If at all possible, use the kerio backup and KMSRecover tools to migrate your data. The two servers should be at approximately the same version (8.3.x, in your case). The reason I recommend this is that it moves ALL the data -- Mail, contacts, calendars, etc. Using this method also means that the mail server will NOT be available to user during the migration, which may take several hours.

If you absolutely have to do this with as little downtime as possible, using a tool like IMAPSYNC can be an alternative. IMAPSYNC does not move calendars, address books, and so forth. We exported these to an external PST file using outlook, then re-imported them to the new account. You also need to know each user's password, so you can put it in the IMAPSYNC script file. All that said, with IMAPSYNC you minimize downtime.




  •  
Maerad

Messages: 147
Karma: 29
Send a private message to this user
Bud Durland wrote on Fri, 11 March 2016 18:21
As someone who has done this kind of thing several times, Please let me make a couple suggestions:

If possible, use Linux for the new mail host. I realize that this is dependent on your expertise and comfort level with Linux vs. Windows, but the performance is much better. I prefer creating the Linux VM, then installing Kerio COnnect, rather than installing the Connect appliance. I'm not implying that WIndows Server won't work, just that IMHO, linux does it better.


That is not really true. I used both Windows Server (2012 in this case) and linux as kerio host, both in a virtual environment (vmware > linux, hyperv > windows) and both servers and kerios were running fine on the same hardware. hyperv and windows server were running as core version, administrated with admin tools and powershell.

No system had any pro or contra, even the ram usage was quite the same, with linux a tiny bit less. Linux was running for around 8 months while windows is still running.

Decided to go for Server 2012, because we upgraded the server (vmware was the free hypervisor and the licence didn't cover more cpu/ram). Also the main reason for Windows right now is the HyperV replica I use for the main server and kerio server - cheapest real time disaster recovery you can get right now. Not to mention the Active Directory integration and AD Tools of Kerio.

When server 2016 is released I might look into linux again, because the replica should be possible even with linux then.

And really, both systems were running more then fine without any performance problems or crashes. Kerio is build on tools, that perform the same on both plattforms including macOS.
  •  
Bud Durland

Messages: 356
Karma: 38
Send a private message to this user
All I can report is what I observed. Our mail store is approximately 1.3GB, with over 4 million messages for 400+/- users. We went from Windows 2008R2 64 bit to Debian 7 64 bit. All the parameters of the VM's were the same -- RAM, CPUs etc. Using the same VM host, and the same storage.

With Linux, the most noticable improvement was with the auto delete task. Suddenly, it could keep up. There was noticeable improvement with web mail performance, and a small improvement in KOFF, although I will admit those last two are strictly "seat of the pants".

We can do AD or Kerberos authentication from the Linux Kerio server, so that is a non issue.
  •  
vindiesel.dd

Messages: 6
Karma: 0
Send a private message to this user
Thanks again for your feedback.

In principle, it doesn't matter if we run kerio on debian/ubuntu linux server or on windows server because i master both systems.

At the moment i prefer to go with Windows Server because the transparent integration of AAA with Microsoft ADS and Kerberos. Our OS X Server is bind to an Microsoft AD too and the Authentication in Kerio Connect is done via Kerberos. From experiance i know that it can be tricky to bring to work LDAP bind with SSL on Linux Services.

In addition there is a better Backup-Support with Windows Server, keyword VSS. We use Veeam to Backup our VMs and do an Application Aware Backup with guest indexing of the Windows VMs.

Regarding to the performance i assume, that there is only a little difference between both systems. I will avoid the Kerio Appliance, because the updates, especially major updates, are not always easy to handle with virtual appliances from some vendors.

As far as i understand you both, you suggest to migrate from os x kerio 8.2.4 patch1 (32Bit) to windows/debian kerio 8.3.4 patch1 (32Bit) and after that to upgrade to windows/debian kerio 9.0.2 (64Bit)?

[Updated on: Sat, 12 March 2016 13:45]

  •  
Bud Durland

Messages: 356
Karma: 38
Send a private message to this user
vindiesel.dd wrote on Sat, 12 March 2016 07:42
As far as i understand you both, you suggest to migrate from os x kerio 8.2.4 patch1 (32Bit) to windows/debian kerio 8.3.4 patch1 (32Bit) and after that to upgrade to windows/debian kerio 9.0.2 (64Bit)?


Yes, That's the path I would recommend. You sound like you've doen your homework, and probably already know this, but if you migrate with the Kerio backup and KMSRecover, don't forget to update your mailserver.cfg file on the Windows server before the first startup. I believe that's covered in the KB article on moving your Kerio Connect installation.
Previous Topic: Accepting/deleting/etc invites via Exchange ActiveSync does not reflect in Kerio
Next Topic: Domain Block List (DBL) 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: Sun Jan 22 19:35:21 CET 2017

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