|
|
Re: Test Migration Failed: libkticonv.2.dylib [message #146500 is a reply to message #146487] |
Wed, 28 August 2019 17:40  |
j.a.duke
Messages: 239 Registered: October 2006
|
|
|
|
Jeff,
Here's my method for doing this migration.
Install same version of Kerio on both systems (so update your new server to 9.2.10 to match the old).
I have my Kerio store folder on the external RAID (probably like you do as well). And Kerio is installed at /usr/local/kerio/mailserver. Kerio is running on the old server. Kerio is installed but not running on the new server.
Setup a new Carbon Copy Cloner backup task on the current server to backup the external HDD RAID to a Remote Macintosh destination (i.e. the new server) and select the SSD RAID there.
Setup another backup task to copy specific files from /usr/local/kerio/mailserver to that same path on the new server. The files/folders you want to copy are:- dbSSL (folder)
- license (folder)
- mailserver.cfg
- mailserver.cfg.bak
- settings (folder)
- sslcert (folder)
- users.cfg
- users.cfg.bak
If you have any custom SpamAssassin rules, you'll want to add the appropriate files from /usr/local/kerio/mailserver/plugins/spamserver/spamassassin/ rules.
You can run these backups while Kerio is running on the old server.
When the cutover time comes, stop Kerio on the old server, run the backups one last time (manually if needed), shutdown the old server, apply static IP from old server to new server (either public or private), then start up Kerio on new server.
I've used this method to migrate 3 or 4 times on one server with great success. And I'm currently using this on my personal Kerio server to keep old and new in synch until I'm ready to cutover.
If you have any questions, please let me know. I'd be more than happy to answer them.
Cheers,
Jon
PS: This procedure (using different platform specific backup tools) should work for Windows & Unix as well.
[Updated on: Wed, 28 August 2019 17:42] Report message to a moderator
|
|
|