Continuing the process of moving from one dspace configuration to a new one ...
I looked over all the update information which looks to be useful if I'm upgrading from 1.4.2 to 1.5.1 on the same machine. However, I'm not sure it answers my question. I have version 1.4.2 on one machine with all the content in it (not a big collection). I have a new machine that now has a working 1.5.1 installation up and running using the xmlui interface. My question is: What are the steps I need to take to move the content from the 1.4.2 machine to the 1.5.1 machine? I have done a postgresql pg_dump of all the content in the database. I'm not sure what to do at this point. Can I just do a restore of the pg_dump output on the new machine or do I have to make some other configuration changes to the 1.5.1 on the new machine first?
Any help will be greatly appreciated. Thanks in advance. The help so far has been great...
Glenn Bunton gbunton@...
Head of Systems Development 757-683-5952
Old Dominion University Libraries
Perry Library - E3.341
Norfolk, VA 23529
To carry repository content over from one version to another, I think
you would have to export the content using DSpace's own tools and
import on the new host. The database schema changed significantly
between 1.4 and 1.5, so a database dump/restore ought to leave you
with a corrupt database and will probably throw all kinds of errors
during the restore phase anyway.
A second problem is that the database is not all there is. You also
need the assetstore, where the actual content files are stored.
If they were my systems, I'd:
1. move the 1.5 setup aside, to have a working model to study in case
things go wrong.
2. shut down old instance temporarily, dump the database, 'tar' up the
[DSpace] directory tree, restart old instance, copy both dumps to
the new host. Forbid any new deposits or metadata changes.
3. unpack [DSpace] tarball in the appropriate place, load database dump.
4. upgrade new instance to 1.5.1 using the documented procedure.
(This step fixes up the database.)
6. cut over production use to the new host. Tell people they can
make changes once more.
If you can get away with it, it would be best to just leave the old
instance down until you are sure the new one works or decide that you
have to fall back and try again. Hmmm, we need a way to temporarily
set a repository read-only....
Mark H. Wood, Lead System Programmer mwood@...
Friends don't let friends publish revisable-form documents.