Difference between revisions of "Upgrading 3.1 to 3.2"
(→How do I do it?) |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Upgrading]] | ||
| + | [[Category:Manual]] | ||
== Why must I do this == | == Why must I do this == | ||
This has always been an essential step of upgrading your EPrints repository. However in 3.2 we are making a particularly big deal about it for two reasons: | This has always been an essential step of upgrading your EPrints repository. However in 3.2 we are making a particularly big deal about it for two reasons: | ||
| Line 8: | Line 10: | ||
It is upgrading the database structure to use UTF8 compatible tables rather than the previous latin1 tables. This means even better and more robust multi-lingual support. It is also adding essential configuration files to your EPrints cfg.d folder. Because EPrints now expects utf8 tables and the new cfg.d files it will not run correctly without performing the following upgrade. | It is upgrading the database structure to use UTF8 compatible tables rather than the previous latin1 tables. This means even better and more robust multi-lingual support. It is also adding essential configuration files to your EPrints cfg.d folder. Because EPrints now expects utf8 tables and the new cfg.d files it will not run correctly without performing the following upgrade. | ||
| + | Thumbnails and document files are now recorded in the database so more technical data can be recorded. That means the upgrader must scan your file system for contained files and add them to the database. This will take some time, depending on the size of your repository. | ||
== How do I do it? == | == How do I do it? == | ||
It's very easy | It's very easy | ||
| Line 17: | Line 20: | ||
Remember ./bin/epadmin upgrade <archive_id> will take serveral hours to run on large repositories because it has to modify every table in the database. | Remember ./bin/epadmin upgrade <archive_id> will take serveral hours to run on large repositories because it has to modify every table in the database. | ||
| − | On success you should see the message Database flag set to 3.2.1. | + | On success you should see the message Database flag set to 3.2.2 (for EPrints 3.2.1). |
| − | If you have any problems let us | + | If you have any problems let us know on EP-Tech. {{EPrintsTech}} |
== Summary == | == Summary == | ||
| Line 33: | Line 36: | ||
* It is recommended that your web server (apache) is offline. | * It is recommended that your web server (apache) is offline. | ||
| − | * The final output of the command should be the version number of the database | + | * The final output of the command should be the version number of the database |
Latest revision as of 14:19, 20 April 2010
Why must I do this
This has always been an essential step of upgrading your EPrints repository. However in 3.2 we are making a particularly big deal about it for two reasons:
- If you do not do it your server will not work
- It takes several hours to do on large databases
What is it doing
It is upgrading the database structure to use UTF8 compatible tables rather than the previous latin1 tables. This means even better and more robust multi-lingual support. It is also adding essential configuration files to your EPrints cfg.d folder. Because EPrints now expects utf8 tables and the new cfg.d files it will not run correctly without performing the following upgrade.
Thumbnails and document files are now recorded in the database so more technical data can be recorded. That means the upgrader must scan your file system for contained files and add them to the database. This will take some time, depending on the size of your repository.
How do I do it?
It's very easy
/etc/init.d/httpd stop ./bin/epadmin upgrade <archive_id> /etc/init.d/httpd start
Remember ./bin/epadmin upgrade <archive_id> will take serveral hours to run on large repositories because it has to modify every table in the database.
On success you should see the message Database flag set to 3.2.2 (for EPrints 3.2.1).
If you have any problems let us know on EP-Tech. For free support and discussion about EPrints you can sign up to EP-Tech.
Summary
- Critical for the successful running of your repo
./bin/epadmin upgrade <archive_id>
- This may take some time dependant on the amount of records in your system and number of revisions.
- The database will be upgraded to be faster and fully UTF8 compatible.
- It is recommended that your web server (apache) is offline.
- The final output of the command should be the version number of the database
