Zarafa 7.1 Migration to Kopano successful, but ...
I was able to migrate my Yaffas Zarafa 7.1 on my Ubuntu 14.04. server to Kopano with your migartion guide (https://kb.kopano.io/display/WIKI/Migrating+from+ZCP+7.1+or+earlier+to+Kopano+Core+8.5+or+later and https://documentation.kopano.io/kopano_migration_manual/zcp_migration.html#manual-zcp-to-kopano-migration). Was quick and painless, maybe because I only got seven users and a small DB :)
It was even possible to upgrade to the recent Kopano version including WebApp and so on.
Since I used Yaffas to install Zarafa all my users are stored in LDAP and I wanted to upgrade the schema: https://documentation.kopano.io/kopano_migration_manual/zcp_migration.html#ldap-data-transplantation-to-new-schema
But now I am puzzled, since that it isn’t working:
# slapcat | sed 's#^zarafa#kopano#' > zarafa2kopano.ldif 5c3f880e UNKNOWN attributeDescription "ZARAFAACCOUNT" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAQUOTAOVERRIDE" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAQUOTAWARN" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAQUOTASOFT" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAQUOTAHARD" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAADMIN" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFASHAREDSTOREONLY" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAHIDDEN" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFAALIASES" inserted. 5c3f880e UNKNOWN attributeDescription "ZARAFASENDASPRIVILEGE" inserted.
it seems the ldif still got Zarafa attributes, e.g.:
dn: uid=familie,ou=People,dc=example,dc=com objectClass: zarafa-user [...] ZARAFAALIASES: email@example.com ZARAFASENDASPRIVILEGE: uid=user1,ou=People,dc=example,dc=com ZARAFASENDASPRIVILEGE: uid=user2,ou=People,dc=example,dc=com ZARAFASENDASPRIVILEGE: cn=Familie_example,ou=Group,dc=example,dc=com ZARAFAQUOTAWARN: 80 ZARAFAQUOTASOFT: 90 ZARAFAQUOTAHARD: 100 ZARAFAQUOTAOVERRIDE: 1 ZARAFAADMIN: 0 ZARAFASHAREDSTOREONLY: 0 ZARAFAHIDDEN: 0
Am I doing something wrong? are those attributes non essential?
is there another guide to complete the migration?
Hi @1of16 ,
that sounds a bit like you had already removed the zarafa schema before running the slapcat command. Instead of this hardcore method of dumping your complete ldap, I would rather recommend to use the script a bit further down in the manual which does an in place update of the defined attributes and object classes.
Generally speaking it will cause no harm to run the Kopano server with the old zarafa schema (you can just reuse your old ldap.cfg).
Hey @fbartels ,
thanks for your fast reply.
Maybe you’re right and due to removing zarafa/yaffas and installing kopano something happened to the schema.
I overlooked the script, I guess I only read “AD” and thought I couldn’t use it.
Since it seems to be recommended I will try to “clean up” my LDAP and will report back :)
Coffee_is_life last edited by Coffee_is_life
i’ve just looket into your sed command and maybe its a bit too easy to be the issue:
first: you wrote “sed s/^zarafa/kopano/ > fileout” but all the attribs are written in upper case.
second: i bet you need to add the g for global, otherwise only the first occurance will be changed… the right command should be:
slapcat |sed 's/^ZARAFA/KOPANO/g' > fileout
if this still wont work maybe go though that file with a loop:
slapcat > /tmp/tempfile.ldif while read line echo $line |sed -e 's/^ZARAFA/KOPANO/g' >> /tmp/zarafa2kopano.ldif done < /tmp/tempfile.ldif
just a guess :)
HI @Coffee_is_life ,
I guess you are right :) didn’t noticed it. maybe it is a good idea to use your brain while fiddeling around with something unknown. but thats what testing system are for…
In the end I maybe just slapcat the ldif file and afterwards sed ZARAFA and zarafa to kopano/KOPANO.
I got a little problem the script further down too:
grep: /usr/share/doc/packages/zarafa/zarafa.schema: Datei oder Verzeichnis nicht gefunden
even more interesting I found the schema here:
this is all a bit confusing, since I 've got no decent experience with ldap.
But I haven’t broken it it, so there is still hope :)
is it possible that there “extra informations” like ZARAFAQUOTAWARN where only used the yaffas and not zarafa itself?
like you already said maybe I shouldn’t care so much about these schemas and just migrate and use it :)