Hi Paul, It's really rather straight forward: 1. Backup your db 2. Get you new installation up and running completely over the default db. 3. Restore db to your new installation (using msyql client, and call it whatever you like so long as you update koha-conf.xml to reflect the new name) 4. Koha will automatically bring the older db up to date after the restore. If you have template customizations, you are in for a bit more of a ride. I think there is a script done by Chris C which may help convert tmpl stuff to tt stuff, but there will probably be much hand work to do after that. Kind Regards, Chris On Wed, Dec 7, 2011 at 11:03 AM, Paul <paul.a@aandc.org> wrote:
We have looked in the manual and the wiki and unfortunately cannot find details on database migration 3.2 to 3.6. We have a production server using 3.2 with some 15,000 biblios (more items) together with staff and patron details, preferences etc.
We have built a new server (Ubuntu 11.10 with mostly Debian Squeeze added modules) LAN only. It is not dedicated to Koha, but also serves several internal websites and databases. All is now fully functional, and we are at the point of running Makefile.PL (i.e, all Perl, Apache, Zebra, MySQL etc has been double checked in preparation for Koha 3.06.01).
We are looking for advice as to:
- at what stage (before or after Koha installation) should we copy over the current kohadb and how should we do this? Preferably we would like to rename it to koha306db.
- is there a detailed write up anywhere on the data migration|conversion for the new template usage?
- any other advice on potential difficulties, errors, pitfalls etc
Thanks - Paul
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha