[horde] Migrating user data from an old horde instance to a new installation
Christian Schoepplein
c.schoepplein at musin.de
Wed Mar 15 10:32:30 UTC 2017
On Fr, Mär 03, 2017 at 10:04:27 +0000, Maurício José T. Tecles wrote:
>Citando Jan Schneider <jan at horde.org>:
>
>>Zitat von Christian Schoepplein <c.schoepplein at musin.de>:
>>
>>>Hi Jan,
>>>
>>>On Fr, Mär 03, 2017 at 03:08:14 +0000, Jan Schneider wrote:
>>>>Zitat von Christian Schoepplein <c.schoepplein at musin.de>:
>>>>>I have a damn old horde installation which has to be migrated to a
>>>>>current setup.
>>>>>
>>>>>Old installation:
>>>>>
>>>>>* Gollem: H3 (1.0.2)
>>>>>* Horde: 3.1.4
>>>>>* Imp: H3 (4.1.4)
>>>>>* Ingo: H3 (1.1.3)
>>>>>* Kronolith: H3 (2.1.4)
>>>>>* Turba: H3 (2.1.5)
>>>>>
>>>>>New setup:
>>>>>
>>>>>* Horde: 5.2.13
>>>>>* Content: 2.0.5
>>>>>* Gollem: H5 (3.0.10)
>>>>>* Imp: H5 (6.2.17)
>>>>>* Ingo: H5 (3.2.13)
>>>>>* Kronolith: H5 (4.2.19)
>>>>>* Nag: H5 (4.2.13)
>>>>>* Timeobjects: 2.1.3
>>>>>* Turba: H5 (4.2.18)
>>>>>
>>>>>Migrating and adapting the config from the old to the new system causes
>>>>>me no trouble, but I am not able to migrate all the userspecific data
>>>>>stored in the mysql db backend.
>>>>>
>>>>>for that reason I see two possebilities now:
>>>>>
>>>>>1. Try again to migrate the database from the old horde setup to the new
>>>>> installation. Because I have no idea what went wrong during the
>>>>> first try, it is very likely that I will run into the same issues
>>>>> again :-(.
>>>>
>>>>Maybe you didn't migrate your data to the last Horde 3 version yet. This is
>>>>the data structure that the automatic migrations from Horde 4 and Horde 5
>>>>expect.
>>>
>>>Yes, I also think that something went wrong during the update to the
>>>latest patchlevel of horde 3.x, but the question is what :-(. There were
>>>so many changes to the database for this old versions of horde and its
>>>applications :-(. How can I find out if I am at the latest patchlevel
>>>for horde 3.x and every application I use?
>>
>>The only way is to manually compare all the documented migrations steps
>>from your Horde 3 version to the latest Horde 3 version with what you have
>>in the database. That's why we invented migrations for Horde 4.
>>
>>>>>2. Start the new installation with an empty database which will be OK,
>>>>> if I at least can migrate the addressbook entries from the old to
>>>>> the new installation. What steps are necessary to do this? Would it
>>>>> also be possible to export the adressbook entries into e.g. vCards,
>>>>> csv files or whatever and import them into the new system via a
>>>>> script or so?
>>>>
>>>>You can always create a custom address book from the old address book
>>>>structure and leave the default address book structure in Turba alone.
>>>
>>>How can this be done?
>>>
>>>The only important data I have to migrate are the addresses, for all
>>>other userspecific data starting from scratch is OK or even the better
>>>solution
>
>I had a similar problem when I did not upgraded to Horde 4. I upgraded from 3
>do 5, but some users did have problem with their agendas or address books.
>Finaly, after a long time, I have a new server installed with up to date
>Debian, installed Horde using Pear, migrated mysql database and it was a
>disaster! Those small problems turned into unusable to several users.
>
>So, my sugestion is that you don't migrate your DB, so you will not keep a
>doubt.
>
>Keep your old system running.
>
>Have your new installation done by Horde install documentation. Create a new
>blank database, create tables using the Horde migration script (see
>documentation).
>
>Set some preferences for Horde and Imp that you think apropriated.
>
>Have your users export their data (agenda, contacts, notes) from old system -
>or make a script to do that for all users (I did'nt do it) - and import then
>into the new system.
Thats the way we'll also do the update here now, migration is inpossible
for what reasons ever :-(. I think horde was installed wrong in the
past, because database tables are missing, e.g. Starting with a new
clean installation and let the users migrate theire data seems the only
way to go :-(.
Cheers,
Christian
--
Christian Schoepplein
Landeshauptstadt Muenchen
Referat fuer Bildung und Sport
Zentrum fuer Informationstechnologie im Bildungsbereich (ZIB)
- Netze und Servermanagement
Postanschrift: Bueroanschrift:
Landeshauptstadt Muenchen Landeshauptstadt Muenchen
Referat fuer Bildung und Sport Referat fuer Bildung und Sport
Postfach Bayerstr. 28 (Raum 5.326)
80313 Muenchen 80335 Muenchen
T: +49 (0)89 233-87623
E: c.schoepplein (at) musin.de
I: http://www.zib.musin.de
Elektronische Kommunikation mit der Landeshauptstadt Muenchen, siehe:
http://www.muenchen.de/ekomm
Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail ausdrucken. Pro
Blatt sparen Sie durchschnittlich 15g Holz, 260ml Wasser, 0,05kWh Strom
und 5g CO2.
More information about the horde
mailing list