Re: Migration from 3.3 to 16.1
"Reitelbach, Thomas" <[email protected]> Sat, 08 Aug 2020 11:13:49 +0200
| Newsgroups | gmane.comp.kde.devel.kroupware |
|---|---|
| Message-ID | <efd60a09f569339bc30434a26f3bc2ef__42710.2805160516$1596878104$gmane$org@erdfunkstelle.de> |
Am 08.08.2020 09:15, schrieb 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 Thank you Tim, i just tried it and it's true, many user settings which were lost before are now restored after i migrated the mysql databases "roundcube" and "kolab" onto the new server. I was afraid of some breaking SQL-changes between 3.3 and 16.1 but it seems to be compatible :) Thank you for your hint regarding the Sieve directory, i had migrated it already together with the imap store and it's already working like a charm. So far everything seems to work, very good. Now I have to do some intense testing before deploying the new server. Cheers Thomas > ------------------------- > > FROM: [email protected] <[email protected]> on > behalf of Reitelbach, Thomas <[email protected]> > SENT: Saturday, August 8, 2020 8:44:41 AM > TO: [email protected] <[email protected]> > 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 > [email protected] > https://lists.kolab.org/mailman/listinfo/users [2] > > > Links: > ------ > [1] https://aka.ms/ghei36 > [2] https://lists.kolab.org/mailman/listinfo/users