Editing Upgrading from 3.1 (section)

==Minimising downtime==

Whilst ''bin/epadmin upgrade'' is running, your repository will be offline.

If you have a LARGE repository the conversion to utf8 can take a LONG time (12+ hours). However some of the tables are volatile (ie. the data can be generated) so you can reduce downtime by clearing these tables beforehand, and then regenerating the content afterwards (whilst your repository is back online).

You only really need to consider this if your eprint__rindex table contains MILLIONS of rows.

Clear these tables before running ''bin/epadmin upgrade'':

 DELETE FROM eprint__rindex;

After running ''bin/epadmin upgrade'' and getting your repository back online:

 bin/epadmin reindex ARCHIVEID eprint

Note that your search won't be at full capacity until the indexes are fully regenerated, but we have found that getting the repository back online ASAP is more desirable so worth the trade off.