Upgrade from Koha 3.08.07
I'm running an extremely antique version of Koha 3.08.07 on Debian Squeeze. For various reasons (mainly the fact that the system is enormously stable) nothing has been upgraded for a long while but it's getting to the point where I need to upgrade it. I'm planning at the same time to move Koha off onto a new system running the latest Ubuntu LTS. I'm happy with installing a brand-new Koha but how do I go about transferring the data. I've found instructions for shifting the database but will the database schema upgrade work with that huge a jump? It's not a huge library, just a couple of thousand books. Thanks for any help that anyone can offer. Nigel
On 09/09/2020 15:34, Nigel Titley wrote:
I'm running an extremely antique version of Koha 3.08.07 on Debian Squeeze.
For various reasons (mainly the fact that the system is enormously stable) nothing has been upgraded for a long while but it's getting to the point where I need to upgrade it. I'm planning at the same time to move Koha off onto a new system running the latest Ubuntu LTS. I'm happy with installing a brand-new Koha but how do I go about transferring the data. I've found instructions for shifting the database but will the database schema upgrade work with that huge a jump? It's not a huge library, just a couple of thousand books.
Thanks for any help that anyone can offer.
And answering my own question, it looks like it might be possible to export the book inventory in MARC format and the Patrons as a CSV file. And possibly the transactions in an offline format? If the worst comes to the worst I can lose the transactions. Does that sound like a plan? Nigel
And answering my own question, it looks like it might be possible to export the book inventory in MARC format and the Patrons as a CSV file. And possibly the transactions in an offline format? If the worst comes to the worst I can lose the transactions.
Does that sound like a plan?
And answering my own question again it looks like that all I have to do is dump the database on the old machine, copy it across and install it on the new machine. The schema upgrade *should* be able to cope as I'm running a koha instance later than 3.4 Nigel
On 09/09/2020 17:24, Nigel Titley wrote:
And answering my own question, it looks like it might be possible to export the book inventory in MARC format and the Patrons as a CSV file. And possibly the transactions in an offline format? If the worst comes to the worst I can lose the transactions.
Does that sound like a plan?
And answering my own question again it looks like that all I have to do is dump the database on the old machine, copy it across and install it on the new machine. The schema upgrade *should* be able to cope as I'm running a koha instance later than 3.4
And this indeed worked... so everyone please ignore my witterings. The procedure I followed was 1. Install latest koha on the new machine 2. Use mysqldump to dump the whole koha database on the old machine 3. Copy across to new machine 4. Use "koha-create --create-db <library>" to create a koha instance on the new machine 5. Drop the new empty database <koha_library> created by step 4 6. Create a new empty database <koha_library> 7. Use mysql to import the dump you made in step 2 into <koha_library> 8. Run koha-upgrade-schema <library> 9. Run koha-rebuild-zebra -v -f <library> 10. Restart apache (possibly not necessary but doesn't do any harm) I now seem to have a fully functional new koha on a new machine Thanks everyone (I know no one said anything but you were all there in spirit) Nigel
Thanks Nigel for reporting your success. I have an upgrade from Ubuntu 16.04 / Koha 17.11 and wonder about such things. In need to clone my VM and try and upgrade but I’ve been putting t off... Your success of a much harder upgrade is very encouraging. Regards Alex Shepherd Sent from my iPad
On 10/09/2020, at 5:14 AM, Nigel Titley <nigel@titley.com> wrote:
On 09/09/2020 17:24, Nigel Titley wrote:
And answering my own question, it looks like it might be possible to export the book inventory in MARC format and the Patrons as a CSV file. And possibly the transactions in an offline format? If the worst comes to the worst I can lose the transactions.
Does that sound like a plan?
And answering my own question again it looks like that all I have to do is dump the database on the old machine, copy it across and install it on the new machine. The schema upgrade *should* be able to cope as I'm running a koha instance later than 3.4
And this indeed worked... so everyone please ignore my witterings. The procedure I followed was
1. Install latest koha on the new machine 2. Use mysqldump to dump the whole koha database on the old machine 3. Copy across to new machine 4. Use "koha-create --create-db <library>" to create a koha instance on the new machine 5. Drop the new empty database <koha_library> created by step 4 6. Create a new empty database <koha_library> 7. Use mysql to import the dump you made in step 2 into <koha_library> 8. Run koha-upgrade-schema <library> 9. Run koha-rebuild-zebra -v -f <library> 10. Restart apache (possibly not necessary but doesn't do any harm)
I now seem to have a fully functional new koha on a new machine
Thanks everyone (I know no one said anything but you were all there in spirit)
Nigel
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Late hi! Yes Nigel, your upgrade steps are exactly what need to be done. However step "10" must be "restart all the things", which is: memcached, apache2 and plack. And, optionally, 11. check the about page if everything is ok ("server information" and "system information" tabs) Enjoy the new features :) Regards, Jonathan Le mer. 9 sept. 2020 à 19:13, Nigel Titley <nigel@titley.com> a écrit :
On 09/09/2020 17:24, Nigel Titley wrote:
And answering my own question, it looks like it might be possible to export the book inventory in MARC format and the Patrons as a CSV file. And possibly the transactions in an offline format? If the worst comes to the worst I can lose the transactions.
Does that sound like a plan?
And answering my own question again it looks like that all I have to do is dump the database on the old machine, copy it across and install it on the new machine. The schema upgrade *should* be able to cope as I'm running a koha instance later than 3.4
And this indeed worked... so everyone please ignore my witterings. The procedure I followed was
1. Install latest koha on the new machine 2. Use mysqldump to dump the whole koha database on the old machine 3. Copy across to new machine 4. Use "koha-create --create-db <library>" to create a koha instance on the new machine 5. Drop the new empty database <koha_library> created by step 4 6. Create a new empty database <koha_library> 7. Use mysql to import the dump you made in step 2 into <koha_library> 8. Run koha-upgrade-schema <library> 9. Run koha-rebuild-zebra -v -f <library> 10. Restart apache (possibly not necessary but doesn't do any harm)
I now seem to have a fully functional new koha on a new machine
Thanks everyone (I know no one said anything but you were all there in spirit)
Nigel
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
On 10/09/2020 08:24, Jonathan Druart wrote:
Late hi!
No problem, better late than never!
Yes Nigel, your upgrade steps are exactly what need to be done. However step "10" must be "restart all the things", which is: memcached, apache2 and plack.
OK... useful to know. I had done a machine reboot which probably took care of that.
And, optionally, 11. check the about page if everything is ok ("server information" and "system information" tabs)
Yes... I did a test check in and check out and got the known error related to Maria/Mysql so followed the excellent wiki article to (fingers crossed) fix the autonumbering problem with INNODB
Enjoy the new features :)
I am! Nigel
participants (3)
-
Alex Shepherd -
Jonathan Druart -
Nigel Titley