EPrints Technical Mailing List Archive
Message: #02644
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Upgrading eprints version to 3.3.12
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: Upgrading eprints version to 3.3.12
- From: Jan Ploski <jpl@plosquare.com>
- Date: Wed, 19 Feb 2014 17:38:46 +0100
Hi, I have upgraded from 3.0.5 to 3.3.12 recently. My procedure was to install the new version over (!) the old installation (e.g. use the existing target directory), which was first copied to the new target machine, then run epadmin upgrade. But I supppose it doesn't really matter - you could also set up a new clean installation and overwrite the empty database with your old one, then epadmin upgrade. Because our repository was large (80,000 records), I also ran truncate subject__index_grep; truncate subject__rindex; truncate eprint__rindex; beforehand and later epadmin reindex <repo> subject epadmin reindex <repo> eprint The epadmin upgrade step took about 1 hour, while the reindexing took more than 6 hours. Because our repository had multiple patches against the 3.0.5 source base, all of them had to be ported and tested beforehand. Some of the "views" definitions had to be upgraded as well. Furthermore, because our repository also contained custom tables not managed by EPrints, data migration (regarding character set) had to be performed manually for those tables, as EPrints only took care of its own (as it should). Overall, it went smoother than expected although some minor late bugs were only discovered after the upgrade and had to be fixed in production. Even so, you should do it on a separate machine, write down a migration plan for later, and keep your production system running until you have made sure the new version is working completely (in our case, the offline QA took several days - the point is you want to do it before, not after the migration). Regards, Jan Ploski Nault, Pierre wrote: > Hi Andrew, > > Once I've installed a clean version of 3.3.12 on the server, what is the rest of the procedure ? A dump of mysql of the production server copied over the new one and then run the /bin/upgrade process ? Any chance that Seb would give me some advice on this ? > > Thanks, > > Pierre > > > > -----Message d'origine----- > De : eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] De la part de Andrew D Bell > Envoyé : 18 février 2014 07:23 > À : eprints-tech@ecs.soton.ac.uk > Objet : [EP-tech] Re: Upgrading eprints version to 3.3.12 > > Hi Pierre, > > It may be that Seb will be able to give you some advice tomorrow, but for now here are our tips: > > Yes, it should run on CentOS 6.5 64 bits. > > You would probably be best to install on a clean system in parallel rather than trying to upgrade in situ. > > Here are some packages that you will need: > yum install mysql mod_perl httpd libxml2 pdf-tools ImageMagick ghostscript ghostscript-fonts mysql-server antiword poppler-utils yum install perl-XML-LibXML perl-Unicode-String perl-CGI perl-Date-Calc perl-Digest-SHA > > Much depends on how much customisation you have done and how cleanly. > > Andrew > > > On 17/02/14 21:00, Nault, Pierre wrote: >> Hi, >> >> We are running on Eprints 3.1-2008-12-03-r3984 on a CentOS 5.10 version. We are thinking on migrating to Eprints 3.3.12 on a CentOS 6.5 64 bits. Regarding these operations, things are not very clear on how to proceed. Can someone shed some lights on these issues: >> >> -Does Eprints 3.3.12 can run on a CentOS 6.5 64 bits ? >> -How do we upgrade Eprints 3.1 to 3.3.12 ? We found http://wiki.eprints.org/w/Moving_a_repository but is there some specifics instructions to take into account when upgrading from 3.1 to 3.3.12 ? >> -Furthermore, which would be the simplest way to achieve this migration of OS and version of Eprints ? Upgrading the OS and then upgrading the Eprints version ? Moving the repo on a Centos 6.5 and then upgrading the Eprints version ? >> >> Your help would be very much appreciated on this matter, >> >> Thanks, >> >> Pierre Nault >> System Librarian >> UQAM Libraries >> Québec/Canada >> >> >> >> *** Options: >> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >> *** Archive: http://www.eprints.org/tech.php/ >> *** EPrints community wiki: http://wiki.eprints.org/ >> *** EPrints developers Forum: http://forum.eprints.org/ > > > -- > Andrew D Bell > EPrints Services > School of Electronics and Computer Science University of Southampton Southampton > SO17 1BJ > > +44 (0)23 8059 8814 > a.d.bell@ecs.soton.ac.uk > > http://www.eprints.org/ > http://eprintsservices.wordpress.com/ > http://twitter.com/EPrintsServices > > *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech > *** Archive: http://www.eprints.org/tech.php/ > *** EPrints community wiki: http://wiki.eprints.org/ > *** EPrints developers Forum: http://forum.eprints.org/ > > *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech > *** Archive: http://www.eprints.org/tech.php/ > *** EPrints community wiki: http://wiki.eprints.org/ > *** EPrints developers Forum: http://forum.eprints.org/
- References:
- [EP-tech] Upgrading eprints version to 3.3.12
- From: "Nault, Pierre" <nault.pierre@uqam.ca>
- [EP-tech] Re: Upgrading eprints version to 3.3.12
- From: Andrew D Bell <a.d.bell@ecs.soton.ac.uk>
- [EP-tech] Re: Upgrading eprints version to 3.3.12
- From: "Nault, Pierre" <nault.pierre@uqam.ca>
- [EP-tech] Upgrading eprints version to 3.3.12
- Prev by Date: [EP-tech] Re: Upgrading eprints version to 3.3.12
- Next by Date: [EP-tech] Re: IRStats 1.0.3. - update_metadata error
- Previous by thread: [EP-tech] Re: Upgrading eprints version to 3.3.12
- Next by thread: [EP-tech] IRStats 1.0.3. - update_metadata error
- Index(es):