[Koha] Our Koha Update Steps

Fred Pierre fred.pierre at smfpl.org
Sat Jun 25 01:40:06 NZST 2011

We recently updated from 3.0 to 3.2 and we are testing a 3.4 installation.
Here are the steps we used to complete the update:

1. Restore data from most recent mysqldump: 30 to 40 minutes
	Employ the drop table list for koha_pro to batch drop individual tables, or
	DROP DATABASE koha_pro ; CREATE DATABASE koha_pro ;
	koha_pro< [path to/] kohamainbakup.sql

2. Run update script to conform database: 20 to 20 minutes


3. [Koha 3.4 UPDATE REQUIRES, not neccessary for earlier version updates!!!]  

   Run data cleanup: 


4. Modify the zebra configuration to allow enough memory to process MARC


  change lines

     /var/lib/zebradb/biblios/register:4G  to 40G
      var/lib/zebradb/biblios/shadow:4G    to 40G

  (we also raised the RAM allocation from 50M to 120M)

5. Rebuild Zebra indexing.

   A. Run as koha user, not as root - requires ./ to run script, perl
directory is kohaclone.

   B. [To prevent cronjob conflict, disable cronjobs, create donotindex
folder, or run from crontab.
       Remember to re-enable these on the working server, so that future
item changes may be indexed for search.]

   ./kohaclone/misc/migration_tools/rebuild_zebra.pl -b -x -r   [Add a -v
for verbose output]
   ./kohaclone/misc/migration_tools/rebuild_zebra.pl -a -r      [Add a -v
for verbose output]

   [Note: The -x rebuilds the xml for the MARC record.]
   If index does not rebuild correctly, run an additional rebuild_zebra.pl
-b to restore the index.

   Check that items are barcode scanning properly. 

   [Our cronjobs index with the -z switch (only updates selected zebraqueue
      instead of the -x -r, which takes longer, however -z only re-indexes
items in the zebraqueue!]

6. Copy over staffglobal.css changes, if customized:


7. Copy over custom page templates - for example, Acqui template
(acqui-home.tmpl) changes:


8. Copy over koha.pm patch, enables status "Available" when item status list
is customized (e.g."MENDING"). 

	/kohaclone/C4/koha.pm      (removes "$selected &&" [line 1006 in the
koha.pm from v3.2])

9. Copy modified staff client login logo to

10. IP addressing: Either  1. New server takes IP address from old server,

	               or  2. Firewall settings need to be adjusted for new server
IP address.

    Apache and MySQL configuration may need to be adjusted in /etc:
mysql/bind.cnf, hosts, apache2/koha

    [Port configuration in koha-conf may need to be adjusted]

11. Update Koha Extras [Applies only to external php custom-script servers
hosting kohaextras3]

   IP address problem: Scripts on the php server are directed to the IP
address of the older version of Koha.

   Either the scripts must be adjusted (search and replace) or the new Koha
must take the IP of the old Koha.

12. Lock down security; harden the web server:

   Restrict access to root account. Limit access to GUI, restrict access to

   Harden Apache configuration. Test remote access filtering, restricted to
specified IP addresses.

-- end --

View this message in context: http://koha.1045719.n5.nabble.com/Our-Koha-Update-Steps-tp4521037p4521037.html
Sent from the Koha - Discuss mailing list archive at Nabble.com.

More information about the Koha mailing list