Surely this fact combines nicely with the "I believe it's about 7 years old now.  The machine has never been upgraded, not even the OS” statement to make an interesting hacking challenge ;o)

I’m hoping you have some form of physical access to the machine?

I’m also hoping it’s all backed up.

Is the database run on the same server? Is that dumped out somewhere too?

First thing I would try and do is get everything backed up to somewhere other than the host system.

Possibly a disk imaging tool (Ghost) might help, and enable you to build a VM of your current system that you can get into?

Sounds like an interesting project – keep us informed of how you get along!

Cheers,

John

Hello,

I have a repository that I set up many years ago and maintenance of which has passed away and back again.  It's an eprints 2 repo that is functioning fine but the administrators would like to upgrade/migrate it to version 3.  I believe it's about 7 years old now.  The machine has never been upgraded, not even the OS.

I have the new hardware but I just can't figure out the best way to achieve this.  I've looked at the migration script written by cjg but I'm worried to try code so old. 

Is there a way to just export everything in a format that can be brought into the latest version? 

If not, then I do have the people available to input old the eprints into the new version.  The only issue with that is that the URLs MUST match the original ones.  This new machine will eventually replace the original, once everything is migrated over.   Is there anyway to directly edit the eprint id of a deposit?

Any suggestions/help would be greatly appreciated.

Thanks,

--
Michael Street     |    Senior Web Consultant    |   Integration, Design and Identity Services - University Information Technology

Suite D, East Office Building  |  York University  |  4700 Keele St. ,  Toronto ON  M3J 1P3 Canada

York UIT will NEVER send unsolicited requests for passwords or other personal information via email.  Messages requesting such information are fraudulent and should be deleted.

*** 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/