Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
Am Sonntag, 3. Juli 2016, 19:17:19 CEST schrieb Martin Steigerwald:
> And I wouldn´t use export/import, it never worked for me.
No, thats not quite accurate, I am not sure I tried it after having read from
many users in upstream mailinglist, that it often does not work. Well I think
I once used it and it was a desaster, but thats really a long, long time ago,
so I am not quite sure. But I think from back then I found that in case you
need to import something: Create a suitable resource for the data you want to
import, point it at the data and let it index it is way more reliable and
faster.
Still the automatic migration will likely always be faster and require less
manual work than any other approach – none in the optimal case, so I suggest
you always just try to let automatic migration do its shop.
Be prepared that it will do a MySQL database schema upgrade, add in new
indexes and also use a two-level file_db_data, so once you upgrade akonadi-
server there is no easy and supported way back. So again, have a backup, just
in case.
And be prepared that it can take a longer time where your Akonadi is basically
busy with the migration and not responding, at least not timely, to anything
else. Depending on whether your system has an SSD, migration may be quite
quick, but for harddisk based systems with huge amounts of mails and a large
MySQL database it can take several hours I think. There may or may not be some
progress indication in Akonadiconsole.
Thanks,
--
Martin
Reply to:
- Prev by Date:
Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
- Next by Date:
Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
- Previous by thread:
Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
- Next by thread:
Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
- Index(es):