Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Server moving on OSX machines
  •  
Spacey

Messages: 156
Karma: -8
Send a private message to this user
Hi!

Actually I'm running my kerio on an slightly older i5 (10.7.5) MacMini and I'm planning to move it to a newer i7 (10.9) one. I've got TimeMachine Backups & Kerio backups itself.

Question now: Does it matter *how* I migrate all the OS & Kerio data?

The easiest way would be the Time Machine (Restore from backup device or smth like that) I guess. Or should I rather setup up the new machine as a new one and re-import the Kerio backup data? Or a complete other way: Use something like Carbon Copy Cloner and then later on update from 10.7 to 10.9?

Which is the best way to go?

Thanks!
  •  
Neil Whiteside (Kerio)

Messages: 318

Karma: 35
Send a private message to this user
Hello Spacey,

This is our recommended method:

http://kb.kerio.com/360

Transfer the server on like-for-like versions, then perform any upgrades to Kerio Connect once the migration is complete. (i.e. If your current server is v8.1.3, install v8.1.3 on the new server; perform the migration, then upgrade Kerio Connect if desired).

I hope this helps.

Best regards,

Neil.

Knowledge Base: http://kb.kerio.com/.
Looking for technical support? http://www.kerio.com/support
  •  
Spacey

Messages: 156
Karma: -8
Send a private message to this user
Thx I'll take a look!
  •  
Spacey

Messages: 156
Karma: -8
Send a private message to this user
OK, once again this topic - I successfully managed to get around this but will go into it the next days.

I prepared the target machine so far. A full backup takes about 12 hours to create. Several questions:

1) After starting the backup what will happen to messages coming in during the backup procedure? Will every message be archived within the last full backup archive? Or will be some lost when re-creating the target server from the backup files?

2) Do I need to turn off Kerio server from receiving messages in order to prevent loss?

My idea was to create a fullbackup which takes long and then an incremental which goes faster.

3) How to recover incremental backups? I've got several files for incremental:
D20140804T074610Z.zip
D20140804T074610Z.1.zip

When I do a

./kmsrecover /Volumes/Kerio-Backup/Kerio-Backups/D20140804T074610Z.zip


only one archiv will be recovered - not the .1 one. Do I need to run the command on that file as well? Does the sequence matter? First the .zip and then the .1.zip?

So my idea was to run a full backup - then recover the full backup on the target machine. Once this is finished turn off the kerio services so the server won't receive any mails anymore and then do a quick incremental backup - recover that on the target machine as well and then switch the hardware.
  •  
Kedar

Messages: 1320
Karma: 48
Send a private message to this user
all your questions are answered in these articles:
http://kb.kerio.com/360
http://kb.kerio.com/1142

1) 2)
"Note that in either scenario, both servers must be taken offline before starting the migration process in order to prevent data inconsistency."

3) do not specify the file, upload the diff backup files to some folder and specify only folder, see knowledge base article 1142 for more.

Your idea with full backup&recovery followed by diff backup&recovery is not recommended, but I see no reason why it should not work.
  •  
Spacey

Messages: 156
Karma: -8
Send a private message to this user
Thanks....

Problem is that full backup & recovery takes about one day - maybe 18h. That's too much off-time. That's the reason for my full & diff recovery - only 1h off-time.

I'll create a test-message in my account - try my method - and will see on the target server if it's there!
  •  
My IT Indy

Messages: 1262
Karma: 40
Send a private message to this user
use rsync.

-
My IT Indy
Kerio Certified Reseller and Hosted Provider
http://www.myitindy.com
  •  
sfpete

Messages: 161
Karma: 9
Send a private message to this user
I would keep this *simple*.

Upgrade your old mini to 10.9.4.

Use Carbon Copy Cloner to do an initial clone of the old one to the new via FireWire TDM (assuming your old one does not have thunderbolt). You can do this while your kerio connect server is live and operational.

When you are ready to switch over, stop kerio on the old. Do one final differential clone... and put the new one up live.

easy.

Previous Topic: Migration from one server to another
Next Topic: Hyperlinks being removed on emails to Yahoo mail
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 Aug 20 00:14:20 CEST 2017

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