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.)
5. test.
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 [email protected]
Friends don't let friends publish revisable-form documents.
pgpEHftxGExue.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
