Lost my Repository

[blandobardo]

I had properly backed up my repository, now I reinstalled OpenKm 2.0 because Openkm 3.0 doesn\'t have the same repository and the conversion from one to another hangs at 70% after more than 4 hours of work..
So I finally decided to reinstall the old OpenKm2.0 and hoped all my data were not lost but after endless fidging with configuration and so on I get a:

\"

Code: Select all

15:24:38,850 ERROR [DirectRepositoryModule] Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager: \'NODE_ID_HI\' is not a column in table or VTI \'APP.VERSION_REFS\'.
javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager: \'NODE_ID_HI\' is not a column in table or VTI \'APP.VERSION_REFS\'.: \'NODE_ID_HI\' is not a column in table or VTI \'APP.VERSION_REFS\'.

\"
all my files now are binary and useless and there\'s no exporting without making openkm2.0 work.. If I try to login I get a \"The repository home /media/raid_data/repository appears to be already locked by the current process.\"

I have opened a forum on the lock issue but I thing the problem is the error before...
I\'ve seen a forum which already questions about Openkm reliability on saving data in binary format: http://www.openkm.com/Usage/509-ReExtra ... e.html#509

hope somebdy helps.. thanks

[jllort]

Seems here you\'ve got some problems with database.

Let\'s try to understand what you\'ve done:
1- Good openkm 2.0 and backup /repository directory ( ok ? )
2- Trying to upgrade to 3.0 but at 70% hangs -> could we see the error log ? ( it\'s normal migration time is longer, because OpenKM rebuilds all data structure, and reindexing files ).
3- You drop upgrade 3.0 and return to 2.0
Here my question is ... you\'ve deleted jboss with okm 2.0 or you\'ve overwrited jboss it\'s not a good idea to overwrite jboss with okm 2.0 with 3.0 and 3.0 with 2.0 because they have several diferent files ( database structure ).

To recover, don\'t delete anything ... please ... on a separate folder download okm 2.0 extract on your server and copy there repository ( not delete ).

For migration if good idea to not delete older installation, install on other folder and then trying migration.

For recovery purposes ( testing backup ) is good idea to make a backup, drop all installation, and try to restore ( please don\'t do it on a production environment, do it on starting up production environment or on testing one ).

[blandobardo]

1) yes, I\'m however not sure if openkm 2a or 2b or simply 2...
2) I issued java -Djava.security.auth.login.config==jaas.config -Xmx1200m -cp OKMUtils.jar es.git.openkm.util.cmd.RepositoryUpgrade /var/www/www/openkm/repository.xml /media/raid_data/repository/ /var/www/openkm/repository.xml /media/raid_data/repository-3.0/
It took more than 3 hours to see it crash without much log other than an error and exit.. don\'t have time to try this for the third time.. I give up
3) I kept my openkm2.0 repository in a separate hard disk through all the time, the openkm and jboss install folders instead got deleted (every 8-9 months I reinstall linux) so I\'m reinstalling from scratch openkm 2.0 and trying to match the old repository..

I need some way to recover my files..don\'t know which way is better..

thankyou

[jllort]

The best way is to starting recovering from OpenKM initial version 2.0, 2.0a 2.0b.

You might not use 2.0a or 2.0b on a production environment.

On your case I\'ll starting trying 2.0 , and then 2.0b and 2.0a. ( Normally we\'ve not made repository changes between beta versions and stable, but I\'m not sure on it ).

About migration time, is normal, during migration process OpenKM recreates all estructure and indexes all files -> that supose an extra time. Althought you\'ve seen some errors during migration process ( java class error ) have you tried this migrated repository, because some error must be considered as warnings.

Josep

[jllort]

Take a look at repository/workspaces/default date time, you could take some idea about which openkm version you downloaded ?

If all fails you can contract our professional services to try recovering it, althought is not a certified installation by us.