GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from https://support.gfi.com.

Home » GFI User Forums » Kerio Connect » Test Migration Failed: libkticonv.2.dylib ( libkticonv.2.dylib cannot load after kmsrecover to copy 9.2.9p1 from Mac 10.10 to 10.14)
icon5.gif  Test Migration Failed: libkticonv.2.dylib [message #146481] Tue, 27 August 2019 14:21 Go to next message
jcooper is currently offline  jcooper
Messages: 113
Registered: May 2009
Location: Syracuse, NY
Hi,

Doing a test migration before I upgrade my server later this month.

Old server is a Mac mini running 10.10 Mavericks with an external HDD RAID.
New is a newer Mac mini with 10.14 Mojave and external SSD RAID.
Both have 9.2.9p1 installed. I have since updated the (old) server to 9.2.10 but the backup is from before the update so I thought it best to keep versions the same then upgrade the new server afterwards.
Old server is fully licensed.
New is a 30 day demo.
New was running fine initially.

I then ran kmsrecover -s /new/store/path /backuppath and rebooted.

System Prefs says it's running.
localhost:4040 won't connect.
I get "Kerio Conneect failed to start because libkticonv.2.dylib could not be loaded" when I run ./mailserver -h or anything from the terminal.
So it's running but it isn't.

Perplexing. Any ideas? Searches here and out on the blogosphere turned up nothing.

Thanks,

Jeff

[Updated on: Tue, 27 August 2019 14:23]

Report message to a moderator

Re: Test Migration Failed: libkticonv.2.dylib [message #146487 is a reply to message #146481] Tue, 27 August 2019 20:26 Go to previous messageGo to next message
jcooper is currently offline  jcooper
Messages: 113
Registered: May 2009
Location: Syracuse, NY
OK, I've given up on the "recommended" method and just copied the files per this link:

https://manuals.gfi.com/en/kerio/connect/content/server-conf iguration/export-and-migration/transferring-an-installation- of-kerio-connect-to-another-server-or-operating-system-360.h tml

But after copying the various config and settings files, it tells me it's unregistered and the trial period is expired (going back to when I first got Kerio in 2005!) and there's no way to get the demo key, which worked before I copied the old server's settings to the new server, into the new installation.

Anyone know of a workaround or a way to run the initial setup on a server that's already been set up so I can add the key?

Thanks,

Jeff
Re: Test Migration Failed: libkticonv.2.dylib [message #146500 is a reply to message #146487] Wed, 28 August 2019 17:40 Go to previous message
j.a.duke is currently offline  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

Previous Topic: Domain Footer - On all email or just Kerio Connect Client?
Next Topic: PDF attachment corruption
Goto Forum:
  


Current Time: Fri Jun 09 00:00:41 CEST 2023

Total time taken to generate the page: 0.01639 seconds