Migration from 3.3 to 16.1

[Tim Haegele]

  Hi,

Some user settings are stored in the db. Like signature, font, ui.

Outside the db the sieve dir might be relevant?

Tim

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: users-bounces at lists.kolab.org <users-bounces at lists.kolab.org> on behalf of Reitelbach, Thomas <tr at erdfunkstelle.de>
Sent: Saturday, August 8, 2020 8:44:41 AM
To: users at lists.kolab.org <users at lists.kolab.org>
Subject: Migration from 3.3 to 16.1

Hello Guys.

currently I'm in progress to migrate a smoothly running Kolab 3.3
community edition with installed multidomain-patches to current Kolab
16.1 community.

My planned migration path is roughly:
1 install a fresh server with bare 16.1
2 tweak new server for multidomain functionality
3 copy over the imap store from old server to new server
4 copy over the ldap database
5 copy over the sql database

So far i've reached top 4 in my plan, which means i've migrated the ldap
onto the new server and i'm able to login via roundcube. I can see all
messages, calendars, shared ressources and folders, sieve scripts
function properly as far as i can see. wonderful :)

But what i'm unsure about is top 5 (migrate SQL).
Can someone tell me if there have been sql changes between kolab 3.3 and
kolab 16.1? Can i simply sqldump the old database on 3.3 and import it
into 16.1?
Do i need to copy the SQL database at all? I don't know what it is used
for anyway, is it the cache? does ist store user configurations?

Can someone with more deep knowledge enlighten me?

Thank you very much :)
_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20200808/a872975f/attachment.html>