Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HideElements
metastrue
commentstrue
childpagestrue
watchtrue
likestrue

Table of Contents

...

Introduction

This document is intended as a base to migrate a Linux server running ZCP  to the latest kopano core Kopano Core version. It does not contain any specific commands as they could vary in different distributions.

Audience

This document is intended to be used by experienced system administrators and engineers who have in-depth knowledge of both Linux and MySQL environments.

Disclaimer

Use these suggestions at your own risk and only if you know what you are doing.

...

Also keep in mind that some steps in this guide can take time depending on the size and complexity of your environment.

 

Preface

Kopano Core is a fork of ZCP 7.2.3. Migrating from ZCP to Kopano Core means that some features and components are replaced and some are dropped

If you are migrating from ZCP 7.1 to KC 8.x, please take the following into account before upgrading:

  • Backups aren't compatible (somewhere we need to make people aware that therefor making (MySQL) backups is very important before migrating)
  • New search is introduced, therefore the index files needs to be re-index, takes time
  • webaccess is dropped, also in ZCP realm ( ZCP7.2.3 release). 
  • No Outlook MAPI clients are being provided by Kopano, but we are compatible with the Zarafa MAPI client.
  • optional but highly recommended:
    • It is possible to run daemon as unprivileged user, if you choose to do this, the attachments needs to be chowned which will also takes some time.
    • Socket location change; Zarafa made this change to adequately implement the support for systemd and run daemons as an unprivileged user.
    • Using the ZCP LDAP schema attributes is perfectly fine, but please keep in mind that new schema changes can be introduced in the future of Kopano Core

Preparations

It is required to purge ZCP
  • are not compatible. We recommend our users to make a MySQL backup before starting the migration procedure.
  • Kopano introduces a new search component with a new index format. Indexes have to be rebuilt, which can take a considerable amount of time.
  • Kopano Core is MAPI based. WebApp, Z-Push and other MAPI based clients (such as Zarafa MAPI client) can be used.
    • Note: not all versions of the Zarafa MAPI Outlook client is compatible with Kopano Core. Make sure all clients are upgraded to the latest version before migrating your Zarafa server to Kopano
  • Optional, but highly recommended steps:
    • Run the daemon as an unprivileged user. Please note this means that the attachements directory needs to be 'chowned'. This can take quite some time.
    • The socket location has changed to implement support for systemd (also required to run daemons as unpriviledged users.
  • Also note: you can use the ZCP LDAP scheme with its attributes. Keep in mind that you might need to migrate the schema if new features require schema changes in the future.

Preparations

The ZCP packages will need to be purged in order to install Kopano Core.  
Make sure you make have a working backup of /etc/zarafa before you start. Also note: the github version of python-zarafa is not compatible with python-kopano so remove any previous version of it (usually located in for example /usr/local/lib/python2.There are repositories available on 7/dist-packages/zarafa)

We recommend that you use our repositories to install/migrate Kopano Core. They are available at https://download.kopano.io/supported/  

Example to add kopano core. 

Debian 8. Use the following examples to configure repositories for your operating system:

Example repository configuration

To add the Kopano Core repository for Debian 8, use:

Code Block
themeMidnight
title/etc/apt/sources.list.d/kopano.list
deb https://<username>serial:<password>@download<KOPANOSERIAL>@download.kopano.io/supported/kopanocore:/final/Debian_8.0/ ./

For Debian-based distributions, we recommend to import the key as well:

Code Block
curl https://downloadserial:<KOPANOSERIAL>@download.kopano.io/supported/core:/final/Debian_8.0/Release.key | apt-key add -

RHEL 7

 

And for Redhat Enterprise Linux 7s

Code Block
themeMidnight
title/etc/yum.repos.d/kopano.repo
[Kopano-Core]
name=Builds of gitfinal masterreleases branches (RHEL_67)
type=rpm-md
baseurl=https://<username>serial:<password>@download<KOPANOSERIAL>@download.kopano.io/supported/kopanocore:/final/RHEL_7/
gpgcheck=0
gpgkey=
enabled=1

SLE SUSE Linux Enterprise Server 12

Code Block
themeMidnight
title /etc/zypp/repos.d/Kopano.repo
[Kopano]
enabled=1
autorefresh=0
baseurl=https://<username>serial:<password>@download<KOPANOSERIAL>@download.kopano.io/supported/kopanocore:/final/SLE_12/
type=rpm-md
[Kopano-webapp]
enabled=0
autorefresh=0
baseurl= waiting for a url
type=rpm-md

 

The github version of python-zarafa is not compatible with python-kopano so remove any previous version of it  (for example in /usr/local/lib/python2.7/dist-packages/zarafa )
 

Install the packages

Install


Installing the packages

You can manually pick the packages you want to install, or install the meta package 'kopano-server-packages'  that . The meta package will install:
 

  • kopano-backup
  • kopano-dagent
  • kopano-gateway
  • kopano-ical
  • kopano-monitor
  • kopano-presence
  • kopano-search
  • kopano-server
  • kopano-spooler
  • kopano-utils

Config file changes

SSL

changes

configuration options

In the configuration files server.cfg, ical.cfg and gateway.cfg “ssl_enable_v2” parameter has become obsolete . Please remove it.Added are the followingand has to be removed.

The following parameters have to be added to these three files:

server_ssl_protocols = !SSLv2
server_ssl_ciphers = ALL:!LOW:!SSLv2:!EXP:!aNULL
server_ssl_prefer_server_ciphers = no
Socket changes

Services configuration

Most daemons are now started using an unprivileged user ;by default. If you want to change this (not recommended), edit the configuration files and modify the 'run_as_user' and 'run_as_group' parameters:

‘run_as_user = kopano’
‘run_as_group = kopano’

 

Check if the user has write access to:

  • /var/lib/kopano/
  • /etc/kopano/
  • /var/log/kopano/
  • /tmp/

Default socket locations have changed to /var/run/kopano/For . All services must use the same socket location, which can be configured in the respective configuration files. For example:

server_socket = /var/run/kopano/server.sock
pid_file = /var/run/kopano/server.pid

Check if Make sure all the configuration files daemons are configured to use the same sockets and run as the same user.

Check if the user has access to:

  • /var/lib/kopano/
  • /etc/kopano/
  • /var/log/kopano/
  • /tmp/

user/group combination as well as the same sockets location!

Migration changes

It is highly recommended that you change the new config file instead of copying the Zarafa files

Attachment location

Make sure you change the  option The default location for attachment storage in Kopano is /var/lib/kopano/attachments/. Move any existing attachments to this directory, or alternatively change the option 'attachment_path' in the server.cfg  to the location where you saved the zarafa attachment or move the attachments to /var/lib/kopano/attachments/
previously stored the Zarafa attachments.

 

If you are running the deamons as unprivileged as an unprivileged user, make sure that the attachments are readable accessible (read/write) by this user. 

SQL database 

The kopano Kopano database is compatible with zarafa so it is not necessary to change this 

Search files 

If the Zarafa database, there are no changes neccesary. Make sure the correct database name is configured.

Search files 

The new default location of the index files is /var/lib/kopano/search/. Make sure there is plenty of disk space available on this filesystem.

  • Note that if you migrate from a ZCP 7.1.x installations,
keep in mind that
  • the kopano-search index format is not compatible with the zarafa-search
.
The new default  location of the index files is /var/lib/kopano/search/(was /var/lib/zarafa/index/).
The new search needs disk space so keep this in mind
  • If you migrate from ZCP 7.2.x, you can either change the option 'index_path' in the search.cfg
 or
  • or you move the index files to /var/lib/kopano/search

For In both options cases, make sure the kopano user is able to access the files (read/write)

Ldap 

LDAP

Kopano Core is capable  to to use  the the zarafa schema, however it is highly recommended that you import and use the kopano-schema. 

If you want to must use the old (Zarafa) schema, then make sure you change '!propmap /etc/zarafakopano/ldap.propmap.cfg'  to  '!propmap /etc/kopanozarafa/ldap.propmap.cfg' in the ldap.cfg configuration file.

Multiserver 

Make sure you change the socket location in the ldap LDAP or Active Directory if you are using a multi server setup

Backup

If you migrate from a ZCP 7.2.1 or lower kopano-backup is not compatible with the old backup files. You will need to recreate backups with the new kopano-backup.

Caching

All the caching values can be copied from the zarafa Zarafa server.cfg

 

 

configuration file.